Re: [PATCH 1/3] autoconf/python_dev: pass include and library dir based on prefix

[Roger Pau Monne <roger.pau@citrix.com>]

Ian Jackson escribió:
> Roger Pau Monne writes ("[Xen-devel] [PATCH 1/3] autoconf/python_dev: pass include and library dir based on prefix"):
>> NetBSD `python-conf --ldflags` doesn't return the library dir, so we
>> have to add it to LDFLAGS based on the prefix returned by `python-conf
>> --prefix`. Also the include dir has been added to CFLAGS using the
>> same technique.
> ...
>>       dnl If python-config is found use it
>> -    CPPFLAGS="$CFLAGS `$PYTHON-config --cflags`"
>> -    LDFLAGS="$LDFLAGS `$PYTHON-config --ldflags`"
>> +    ac_python_prefix=`$PYTHON-config --prefix`
>> +    CPPFLAGS="$CFLAGS `$PYTHON-config --cflags` -I$ac_python_prefix/include"
>> +    LDFLAGS="$LDFLAGS `$PYTHON-config --ldflags` -L$ac_python_prefix/lib"
>
> Shouldn't the -I and particulary the -L come first ?

According to man ld (from Debian):

"All -L options apply to all -l options, regardless of the order in 
which the options appear."

So it should be ok to specify -L after -l.

> TBH I'm
> surprised that this works since it looks like it ought to generate
>     -lpython2.6 -L/usr/blah/lib/bleh/python2.6
> or something, which I wouldn't expect to work.

python-config --prefix on the systems I've tested (that's NetBSD and 
Debian) returns the prefix path used for install, that's /usr on Debian 
and /usr/pkg on NetBSD.

Anyway, forget about this patch, a latter patch 3/3, fixes the library 
path search, so it's just easier to pass APPEND_LIB=/usr/pkg/lib to 
configure rather than touching the python_dev code.