Bug#661658: cctools: FTBFS on kfreebsd
On Tue, Mar 27, 2012 at 09:44:01PM +0200, Julien Cristau wrote: On Tue, Mar 27, 2012 at 09:50:14 +0200, Michael Hanke wrote: Maybe a simple rebuild attempt would fix it (CC'ing the wb-team)? gb cctools_3.4.2-1 . kfreebsd-amd64 kfreebsd-i386 Done. Error remains the same -- need to look more closely. Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
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-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
On 30/03/12 10:43, Michael Hanke wrote:
but on kfreebsd it does:
asdfasdf% python sysconfig_freebsd_demo.py
Empty CFLAGS
asdfasdf% CFLAGS='obscure' python sysconfig_freebsd_demo.py
No CFLAGS variable
Hi,
I'm not seeing that problem on kfreebsd-i386, at least?
steven@kfreebsd-i386:~$ python2.7
Python 2.7.2+ (default, Dec 1 2011, 02:13:40)
[GCC 4.6.2] on gnukfreebsd8
Type help, copyright, credits or license for more information.
from distutils import sysconfig; print(sysconfig.get_config_var('CFLAGS'))
-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
steven@kfreebsd-i386:~$ dpkg -s python2.7-minimal
Package: python2.7-minimal
Status: install ok installed
Priority: optional
Section: python
Installed-Size: 5014
Maintainer: Matthias Klose d...@debian.org
Architecture: kfreebsd-i386
Source: python2.7
Version: 2.7.2-8
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
On Fri, Mar 30, 2012 at 01:30:16PM +0100, Steven Chamberlain wrote: On 30/03/12 10:43, Michael Hanke wrote: but on kfreebsd it does: asdfasdf% python sysconfig_freebsd_demo.py Empty CFLAGS asdfasdf% CFLAGS='obscure' python sysconfig_freebsd_demo.py No CFLAGS variable Hi, I'm not seeing that problem on kfreebsd-i386, at least? Interesting. I got the above output on asdfasdf.debian.net's unstable chroot (kfreebsd-amd64, AFAIK). Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
I'm not seeing that problem on kfreebsd-i386, at least? Interesting. I got the above output on asdfasdf.debian.net's unstable chroot (kfreebsd-amd64, AFAIK). The key difference might be exact python version. Inside sid chroot: python2.6 2.6.7-4 python2.7 2.7.2-11 asdfasdf:~$ CFLAGS='obscure' python2.6 x.py CFLAGS='-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes' asdfasdf:~$ CFLAGS='obscure' python2.7 x.py No CFLAGS variable asdfasdf:~$ python2.6 x.py CFLAGS='-fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes' asdfasdf:~$ python2.7 x.py Empty CFLAGS Petr -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
On 30/03/12 14:19, Petr Salinger wrote: Inside sid chroot: python2.6 2.6.7-4 python2.7 2.7.2-11 Thanks. This was probably debian/patches/issue9189.diff, which was introduced in 2.7.2-10 and re-jigged for 2.7.3. Not sure there's any point reporting a bug. The python2.7 transition (to 2.7.3) seems nearly complete anyway; just waiting on a fix for a different NeuroDebian package: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631856 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
On Fri, Mar 30, 2012 at 02:19:24PM +0100, Steven Chamberlain wrote: On 30/03/12 14:19, Petr Salinger wrote: Inside sid chroot: python2.6 2.6.7-4 python2.7 2.7.2-11 Thanks. This was probably debian/patches/issue9189.diff, which was introduced in 2.7.2-10 and re-jigged for 2.7.3. Not sure there's any point reporting a bug. The python2.7 transition (to 2.7.3) seems nearly complete anyway; just waiting on a fix for a different NeuroDebian package: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631856 This is next on the list! Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
On Fri, Mar 30, 2012 at 11:43:23 +0200, Michael Hanke wrote:
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'
--
That's not a BSD problem I think, it's #656118, which is fixed in newer
versions of python2.7, but newer versions FTBFS on kfreebsd.
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#661658: cctools: FTBFS on kfreebsd
Hi, [sorry for the delay] On Wed, Feb 29, 2012 at 12:13:17AM +0100, Julien Cristau wrote: Source: cctools Version: 3.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The relevant parts seem to be: checking for /usr/include/python2.7/Python.h...yes found python development libraries Traceback (most recent call last): File stdin, line 4, in module AttributeError: 'NoneType' object has no attribute 'split' I ran the respective bit of python code on asdfasdf.d.n and cannot reproduce the failure with Python 2.7. Maybe this was a transient issue in the kfreebsd port that is no longer present in today's unstable. Maybe a simple rebuild attempt would fix it (CC'ing the wb-team)? gb cctools_3.4.2-1 . kfreebsd-amd64 kfreebsd-i386 thanks, Michael -- Michael Hanke http://mih.voxindeserto.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661658: cctools: FTBFS on kfreebsd
On Tue, Mar 27, 2012 at 09:50:14 +0200, Michael Hanke wrote: Hi, [sorry for the delay] On Wed, Feb 29, 2012 at 12:13:17AM +0100, Julien Cristau wrote: Source: cctools Version: 3.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The relevant parts seem to be: checking for /usr/include/python2.7/Python.h...yes found python development libraries Traceback (most recent call last): File stdin, line 4, in module AttributeError: 'NoneType' object has no attribute 'split' I ran the respective bit of python code on asdfasdf.d.n and cannot reproduce the failure with Python 2.7. Maybe this was a transient issue in the kfreebsd port that is no longer present in today's unstable. Maybe a simple rebuild attempt would fix it (CC'ing the wb-team)? gb cctools_3.4.2-1 . kfreebsd-amd64 kfreebsd-i386 Done. Cheers, Julien signature.asc Description: Digital signature
Bug#661658: cctools: FTBFS on kfreebsd
Source: cctools Version: 3.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) See the build logs at https://buildd.debian.org/status/package.php?p=cctools The relevant parts seem to be: checking for /usr/include/python2.7/Python.h...yes found python development libraries Traceback (most recent call last): File stdin, line 4, in module AttributeError: 'NoneType' object has no attribute 'split' [...] make[4]: Entering directory `/build/buildd-cctools_3.4.2-1-kfreebsd-amd64-_rkrQ0/cctools-3.4.2/work_queue/src/python' SWIG work_queue.i (python) gcc -fPIC -c work_queue_wrap.c -o work_queue_wrap.o -I../../../dttools/src work_queue_wrap.c:125:20: fatal error: Python.h: No such file or directory compilation terminated. make[4]: *** [work_queue_wrap.o] Error 1 Cheers, Julien signature.asc Description: Digital signature
