[Python-Dev] autoconf question: howto add to CFLAGS and LDFLAGS? (original) (raw)
Trent Mick trentm@ActiveState.com
Wed, 16 Aug 2000 16:55:42 -0700
- Previous message: [Python-Dev] Pending patches for 2.0
- Next message: [Python-Dev] autoconf question: howto add to CFLAGS and LDFLAGS?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello autoconf-masters,
I am currently trying to port Python to Monterey (64-bit AIX) and I need to add a couple of Monterey specific options to CFLAGS and LDFLAGS (or to whatever appropriate variables for all 'cc' and 'ld' invocations) but it is not obvious at all how to do that in configure.in. Can anybody helpme on that?
ANother issue that I am having. This is how the python executable is linked on Linux with gcc:
gcc -Xlinker -export-dynamic python.o ../libpython2.0.a -lpthread -ldl -lutil -lm -o python
It, of course, works fine, but shouldn't the proper (read "portable") invocation to include the python2.0 library be
gcc -Xlinker -export-dynamic python.o -L.. -lpython2.0 -lpthread -ldl -lutil -lm -o python
That invocation form (i.e. with the '-L.. -lpython2.0') works on Linux, and is required on Monterey. Does this problem not show up with other Unix compilers. My hunch is that simply listing library (*.a) arguments on the gcc command line is a GNU gcc/ld shortcut to the more portable usage of -L and -l. Any opinions. I would either like to change the form to the latter or I'll have to special case the invocation for Monterey. ANy opinions on which is worse.
Thanks, Trent
-- Trent Mick TrentM@ActiveState.com
- Previous message: [Python-Dev] Pending patches for 2.0
- Next message: [Python-Dev] autoconf question: howto add to CFLAGS and LDFLAGS?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]