durusmail: durus-users: Problem compiling Durus on Tiger
Problem compiling Durus on Tiger
2005-06-22
2005-06-22
2005-06-22
2005-06-22
2005-06-22
2005-06-22
2005-06-24
Problem compiling Durus on Tiger
David Binger
2005-06-22
On Jun 22, 2005, at 6:32 AM, Mario Ruggier wrote:

> Hi,
>
> i was trying to install durus 2.0 on a clean OS X Tiger powerbook
> (not mine ;-( and the build step reports the following:
>
> building 'durus._persistent' extension
> gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-
> fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-
> prototypes -I/System/Library/Frameworks/Python.framework/Versions/
> 2.3/include/python2.3 -c _persistent.c -o build/temp.darwin-8.1.0-
> Power_Macintosh-2.3/_persistent.o
> _persistent.c:6:20: Python.h: No such file or directory
> _persistent.c:7:26: structmember.h: No such file or directory
> .....
>
> The gcc being used is gcc-3.3, but i also tried with gcc-4.0.
>
> These files should come from the python installation?
> It is using the one that "comes" with the system, i.e.:
>
> $ python
> Python 2.3.5 (#1, Mar 20 2005, 20:38:20)
> [GCC 3.3 20030304 (Apple Computer, Inc. build 1809)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> >>>
>
> but, as the machine was "initialised" from an older powerbook that
> was running panther, I have no idea if there is some confusion
> between the 2.
>
> BTW, same problem when trying to install quixote.
>
> How do I fix this?

My python seems to be the same build, also on Tiger, and the
extension-building
is working.  On my machine, the Python.h file appears in
/System/Library/Frameworks/Python.framework/Versions/2.3/include/
python2.3
and also in
/System/Library/Framework/Headers.
I believe the compiler should be finding those files in the first of
these directories,
since it names that directory in the "-I" flag.

I'm guessing that the
/System/Library/Frameworks/Python.framework/Versions/2.3/include/
python2.3
directory on your machine doesn't have the same header files as it
does on mine.
If so, putting the correct header files there would fix this problem.

Here is some info from my machine:

$ python setup.py build_ext
running build_ext
building 'durus._persistent' extension
creating build
creating build/temp.darwin-8.1.0-Power_Macintosh-2.3
gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-
madd -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -
I/System/Library/Frameworks/Python.framework/Versions/2.3/include/
python2.3 -c _persistent.c -o build/temp.darwin-8.1.0-
Power_Macintosh-2.3/_persistent.o
creating build/lib.darwin-8.1.0-Power_Macintosh-2.3
creating build/lib.darwin-8.1.0-Power_Macintosh-2.3/durus
gcc -Wl,-F. -Wl,-F. -bundle -undefined dynamic_lookup build/
temp.darwin-8.1.0-Power_Macintosh-2.3/_persistent.o -o build/
lib.darwin-8.1.0-Power_Macintosh-2.3/durus/_persistent.so

$ python
Python 2.3.5 (#1, Mar 20 2005, 20:38:20)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1809)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>>

$ ls -l /System/Library/Frameworks/Python.framework/Versions/2.3/
include/python2.3/Python.h
-rw-r--r--   1 root  wheel  3927 Mar 20 23:47 /System/Library/
Frameworks/Python.framework/Versions/2.3/include/python2.3/Python.h


reply