Re: FTBFS: python

2003-12-10 Thread Duck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Coin, "M. Gerards" <[EMAIL PROTECTED]> writes: > And if you have no idea how to debug or if you just don't want to do this > can you please isolate the problem? In that case you just have to write a > small test program in C which triggers the probl

Re: FTBFS: python

2003-11-26 Thread M. Gerards
Quoting "Alfred M. Szmidt" <[EMAIL PROTECTED]>: >I'm looking at the thread problem but it is really tricky. I tried >disabling threads totaly using --without-threads but it didn't >worked at all. I really wonder what this configure is really >doing... > > Could you try debugging

Re: FTBFS: python

2003-11-26 Thread Alfred M. Szmidt
This one solves the linking problem with libX11 : (i mean the clean way, not using LD_LIBRARY_PATH as someone told me) This is the clean way currently... I'm looking at the thread problem but it is really tricky. I tried disabling threads totaly using --without-threads but it didn't

Re: FTBFS: python

2003-11-25 Thread Santiago Vila
> I made 2 minor patches for python2.3 and hope this will be useful. > > This one solves the linking problem with libX11 : > (i mean the clean way, not using LD_LIBRARY_PATH as someone told me) Currently, you have to use LD_LIBRARY_PATH to run any X binary. This is a general problem which is not s

Re: FTBFS: python

2003-11-25 Thread Duck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Coin, I made 2 minor patches for python2.3 and hope this will be useful. This one solves the linking problem with libX11 : (i mean the clean way, not using LD_LIBRARY_PATH as someone told me) - ---

Re: FTBFS: python

2003-11-20 Thread Michael Banck
On Thu, Nov 20, 2003 at 04:47:05PM +0100, Santiago Vila wrote: > The problem, as I see it, is that the current code is trying to use > both cthreads and pthreads, hence the mess. We would need to change > configure.in and such so that pthreads is always used everywhere. I don't remember exactly, b

Re: FTBFS: python

2003-11-20 Thread Santiago Vila
On Thu, 20 Nov 2003, Robert Millan wrote: > On Wed, Nov 19, 2003 at 11:56:06PM +0100, Santiago Vila wrote: > > It's Debian who decided (implicitly, by not special-casing the Hurd) that > > the Debian python package (for which I asked for help to compile) should be > > compiled with threads support

Re: FTBFS: python

2003-11-20 Thread Robert Millan
On Wed, Nov 19, 2003 at 11:56:06PM +0100, Santiago Vila wrote: > > Indeed. > > It's Debian who decided (implicitly, by not special-casing the Hurd) that > the Debian python package (for which I asked for help to compile) should be > compiled with threads support. > > Perhaps we should ask oursel

Re: FTBFS: python

2003-11-19 Thread Santiago Vila
On Wed, 19 Nov 2003, Robert Millan wrote: > On Mon, Nov 17, 2003 at 02:10:07PM +0100, Alfred M. Szmidt wrote: > > [Moving this to bug-hurd since this has nothing todo with Debian] > > Ok but don't drop the CC, it's still a porting issue Debian is interested in. Indeed. It's Debian who decided (i

Re: FTBFS: python

2003-11-19 Thread Robert Millan
On Mon, Nov 17, 2003 at 02:10:07PM +0100, Alfred M. Szmidt wrote: > [Moving this to bug-hurd since this has nothing todo with Debian] Ok but don't drop the CC, it's still a porting issue Debian is interested in. >> python: ../../libpthread/sysdeps/generic/pt-mutex-timedlock.c:55: > __pthread

Re: FTBFS: python

2003-11-17 Thread Duck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Santiago Vila <[EMAIL PROTECTED]> writes: > And this is what happens when compiling python2.3: > > gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -fno-strict-aliasing > -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/include/tcl8.4 -I/usr/X11R6/include -I.

Re: FTBFS: python

2003-11-06 Thread Neal H. Walfield
I just remember there being issues about constructors not being called if -lpthread was not on the link line. I think perl did this but I forget.

Re: FTBFS: python

2003-11-06 Thread Santiago Vila
On Sun, 2 Nov 2003, Neal H. Walfield wrote: > At Sun, 2 Nov 2003 19:53:31 +0100 (CET), > Santiago Vila wrote: > > > > And this is what happens when compiling python2.3: > > > > gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -fno-strict-aliasing > > -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/includ

Re: FTBFS: python

2003-11-02 Thread Neal H. Walfield
At Sun, 2 Nov 2003 19:53:31 +0100 (CET), Santiago Vila wrote: > > And this is what happens when compiling python2.3: > > gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -fno-strict-aliasing > -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/include/tcl8.4 -I/usr/X11R6/include -I. > -I/build/buildd/pyth

FTBFS: python

2003-11-02 Thread Santiago Vila
And this is what happens when compiling python2.3: gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -fno-strict-aliasing -DWITH_APPINIT=1 -DWITH_BLT=1 -I/usr/include/tcl8.4 -I/usr/X11R6/include -I. -I/build/buildd/python2.3-2.3.2/./Include -I/build/buildd/python2.3-2.3.2/Include -I/build/bu