Issue 124156 - Python is not correctly detected by configure on OS X
Summary: Python is not correctly detected by configure on OS X
Status: UNCONFIRMED
Alias: None
Product: Build Tools
Classification: Code
Component: configure (show other issues)
Version: 4.1.0-dev
Hardware: Mac OS X 10.9
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-31 17:28 UTC by Ted Ralphs
Modified: 2014-02-13 14:24 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Patch for configure.in (1.55 KB, patch)
2014-01-31 17:28 UTC, Ted Ralphs
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this issue.
Description Ted Ralphs 2014-01-31 17:28:20 UTC
Created attachment 82456 [details]
Patch for configure.in

Python headers are not in a standard system directory on OS X and the variable $python_include is not set correctly due to the interaction of what appear to me to be two different bugs:

1. The path to the python interpreter is stored in the variable $_python, but the command for getting the include directory calls $PYTHON instead, which is not set (at least in some cases).

2. The value of $python_include is only set if

test -n "$with_system_python" -o -n "$with_system_libs" && \
        test "$with_system_python" != "no"

evaluates to true, which requires $with_system_libs to also be set, which it is not (at least in my use case). 

The fix is to set $python_include inside the following if block, which only tests

test "$with_system_python" = "yes"

A patch is attached that allowed Open Office to build on OS X. The configure command I used is

./configure --with-dmake-url=http://dmake.apache-extras.org.codespot.com/files/dmake-4.12.tar.bz2 --with-epm-url=http://www.msweet.org/files/project2/epm-3.7-source.tar.gz --with-macosx-sdk-version=10.9 --without-junit
Comment 1 jsc 2014-02-13 14:24:20 UTC
remove the blocker flag and change back to normal.

Build issues are serious and we work on it asap but if we can build on our release build systems it is not blocker but a normal issue.

Nevertheless thank you for the patch. We will take care of it asap or latest after 4.1.