On Fri, Mar 30, 2012 at 10:52:53AM +0200, Michael Hanke wrote:
> Error remains the same -- need to look more closely.
I found the issue causing #661658. The python sysconfig package behaves
different on kfreebsd -- I think one could call this a bug (CC'ing -bsd
list). This little script shows the difference:
----------------------
from distutils import sysconfig
cflags = sysconfig.get_config_var('CFLAGS')
if cflags is None:
print 'No CFLAGS variable'
elif cflags:
print "CFLAGS='%s'" % cflags
else:
print 'Empty CFLAGS'
----------------------
Running on linux-i386 does:
% python sysconfig_freebsd_demo.py
CFLAGS='-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes'
% CFLAGS="obscure" python sysconfig_freebsd_demo.py
CFLAGS='-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes'
but on kfreebsd it does:
asdfasdf% python sysconfig_freebsd_demo.py
Empty CFLAGS
asdfasdf% CFLAGS='obscure' python sysconfig_freebsd_demo.py
No CFLAGS variable
as far as I understand what it is supposed to do, I'd say that both
calls should yield the same result (at least), I tend to think that both
times CFLAGS should be defined, but for sure having a runtime CFLAGS env
var should not change the return value.
Regarding the cctools FTBFS this is easy to work around -- I'll upload a
fix later today. Regarding the cause of this problem, it would be nice
if a BSD porter could take a look and judge this a bug or not.
Cheers,
Michael
--
Michael Hanke
http://mih.voxindeserto.de
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120330094323.GC10406@meiner
