problem building Python in MachTen Unix

William C. Brennan brennanw at pond.com
Sun Apr 30 13:43:12 EDT 2000


Please, someone save me from Perl!

I'm trying to build Python from sources to work under Tenon's CodeBuilder
Unix (MachTen Lite), which is a BSD variety which runs under the MacOS.  
(Yes, Unix _under_ the MacOS).  I want to use Python because I'm
frustrated by my inability to understand even my own Perl scripts, let alone
other folks'.  Python looks like it has everything I want.

I've downloaded and unpacked the Python source, and run the configure
script without error.  Among the many lines of information, it displays:

   checking for --with-next-framework... no
   checking for --with-dyld... required for framework build

When I proceed to performing the "make", I get an error while making the
object files in tho Python sub-directory:

   gcc -g -O2 -I./../Include -I.. -DHAVE_CONFIG_H   -c getversion.c -o getversion.o
   gcc -g -O2 -I./../Include -I.. -DHAVE_CONFIG_H   -c graminit.c -o graminit.o
   gcc -g -O2 -I./../Include -I.. -DHAVE_CONFIG_H   -c import.c -o import.o
   gcc -c -g -O2 -I./../Include -I.. -DHAVE_CONFIG_H -I/ ./importdl.c
   ./importdl.c:269: mach-o/dyld.h: No such file or directory
   make[1]: *** [importdl.o] Error 1
   make[1]: Leaving directory `/my/Python-1.5.2/Python'

which implies to me that the configure script thinks my "with-dyld" or 
"with-next-framework" settings are set.  It looks like I need to tell the 
configure script that I'm running without frameworks and without dyld, 
but my attempts to communicate this to the configure script have failed.  
I've tried:

  ./configure --without-next-framework --without-dyld

which has worked even less well.  I've also tried manually editing the configure 
script (which is almost totally unintelligible to me) by changing the defaults
at the top from:

   ac_help="$ac_help
   --with-next-framework     Build (OpenStep|Rhapsody|MacOS10) framework"
   ac_help="$ac_help
   --with-dyld               Use (OpenStep|Rhapsody|MacOS10) dynamic linker"
to
   ac_help="$ac_help
   --without-next-framework     Build (OpenStep|Rhapsody|MacOS10) framework"
   ac_help="$ac_help
   --without-dyld               Use (OpenStep|Rhapsody|MacOS10) dynamic linker"

which hasn't worked either.  I've looked through the configure script to
see if I could figure out any other flags which may indirectly cause
"with-next-framwork" or "with-dyld" to be set, but I can't find anything.

Could someone suggest something to this naive Python builder to get his
"make" script to work?

Thanks!

-- bill


-- 
Bill Brennan
brennanw at pond.com




More information about the Python-list mailing list