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
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/
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 s
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
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
>
>
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:
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
7 matches
Mail list logo
