Re: Initial list of ports that fail due to -pthread

2003-09-25 Thread Christian Weisgerber
Kris Kennaway <[EMAIL PROTECTED]> wrote: > mp3blaster-3.1.3 I have a patch, will talk to maintainer. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listin

Re: Initial list of ports that fail due to -pthread

2003-09-24 Thread Michael Nottebrock
On Wednesday 24 September 2003 19:36, Bruce M Simpson wrote: > On Wed, Sep 24, 2003 at 06:14:52PM +0200, Michael Nottebrock wrote: > Content-Description: signed data > > > On Wednesday 24 September 2003 04:18, Kris Kennaway wrote: > > > icecast-1.3.12_1 > > > > I don't have a -CURRENT machine to te

Re: Initial list of ports that fail due to -pthread

2003-09-24 Thread Bruce M Simpson
On Wed, Sep 24, 2003 at 06:14:52PM +0200, Michael Nottebrock wrote: Content-Description: signed data > On Wednesday 24 September 2003 04:18, Kris Kennaway wrote: > > > icecast-1.3.12_1 > > I don't have a -CURRENT machine to test with. I don't mind the port marked > BROKEN, since it's unsupported

Re: Initial list of ports that fail due to -pthread

2003-09-24 Thread Michael Nottebrock
On Wednesday 24 September 2003 04:18, Kris Kennaway wrote: > icecast-1.3.12_1 I don't have a -CURRENT machine to test with. I don't mind the port marked BROKEN, since it's unsupported abandonware and due for deorbit anyway. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/

Re: Initial list of ports that fail due to -pthread

2003-09-24 Thread Michael Edenfield
* Will Andrews <[EMAIL PROTECTED]> [030924 01:50]: > On Wed, Sep 24, 2003 at 01:34:13AM -0400, Michael Edenfield wrote: > > One very important group of ports that should get looked at when this > > gets worked out is KDE. Apparently, Qt uses a different means of > > determining wether to use threa

Re: Initial list of ports that fail due to -pthread

2003-09-24 Thread Morten Rodal
On Tue, Sep 23, 2003 at 07:18:21PM -0700, Kris Kennaway wrote: > pwlib-1.5.0_2 I have sent patches for pwlib and gnomemeeting to the maintainer shortly after the gnome2.4 import, and he said they would be commited (with a slight modification) when the ports freeze was lifted. -- Morten Rodal __

Re: Initial list of ports that fail due to -pthread

2003-09-24 Thread Sergey Matveychuk
Kris Kennaway wrote: Here is a partial list of the ports that need to be taught to respect PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I [skipped] omniORB-4.0.2 PR/56862 is waiting for ports unfreezing. -- Sem. ___ [EMAIL PROTEC

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Stijn Hoop
On Wed, Sep 24, 2003 at 02:11:53AM -0400, Daniel Eischen wrote: > On Wed, 24 Sep 2003, Stijn Hoop wrote: > > Just an idea (I hope this hasn't been said before in the mega thread but at > > least I didn't get it this way): > > > > - fix all ports to respect PTHREAD_LIBS _ON THE LINKING STAGE_ (so n

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Daniel Eischen
On Wed, 24 Sep 2003, Stijn Hoop wrote: > On Wed, Sep 24, 2003 at 01:49:50AM -0400, Daniel Eischen wrote: > > If FreeBSD wants to take the simple approach and only support > > one thread library in ports (-pthread == -lpthread) and not > > make it selectable via PTHREAD_LIBS, then its not a problem

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread John Birrell
On Wed, Sep 24, 2003 at 08:01:35AM +0200, Stijn Hoop wrote: > - fix all ports to respect PTHREAD_LIBS _ON THE LINKING STAGE_ (so no > global search & replace, for it shouldn't be used in compile command lines) > - keep '-pthread' as a compiler option, which maps to a NOOP for compiling > and '-

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Daniel Eischen
On Wed, 24 Sep 2003, John Birrell wrote: > On Wed, Sep 24, 2003 at 01:49:50AM -0400, Daniel Eischen wrote: > > It would be nice to be able to support all our thread > > libraries, but I grow weary. > > I grow weary yesterday. You've just been around a little longer than I have! -- Dan Eischen

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Stijn Hoop
On Wed, Sep 24, 2003 at 01:49:50AM -0400, Daniel Eischen wrote: > If FreeBSD wants to take the simple approach and only support > one thread library in ports (-pthread == -lpthread) and not > make it selectable via PTHREAD_LIBS, then its not a problem. > It would be nice to be able to support all o

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread John Birrell
On Wed, Sep 24, 2003 at 01:49:50AM -0400, Daniel Eischen wrote: > It would be nice to be able to support all our thread > libraries, but I grow weary. I grow weary yesterday. -- John Birrell ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/m

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Daniel Eischen
On Wed, 24 Sep 2003, Michael Edenfield wrote: > * Kris Kennaway <[EMAIL PROTECTED]> [030923 22:21]: > > > Here is a partial list of the ports that need to be taught to respect > > PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I > > just grepped for the "-pthread is deprecate

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Will Andrews
On Wed, Sep 24, 2003 at 01:34:13AM -0400, Michael Edenfield wrote: > One very important group of ports that should get looked at when this > gets worked out is KDE. Apparently, Qt uses a different means of > determining wether to use threading, than the ports that depend on it. > The qt-using port

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Michael Edenfield
* Kris Kennaway <[EMAIL PROTECTED]> [030923 22:21]: > Here is a partial list of the ports that need to be taught to respect > PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I > just grepped for the "-pthread is deprecated" error message). None of One very important group of

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Daniel Eischen
On Wed, 24 Sep 2003, John Birrell wrote: > On Tue, Sep 23, 2003 at 07:33:43PM -0700, Kris Kennaway wrote: > > Won't these ports still need to be fixed to look at > > PTHREAD_{LIBS,CFLAGS} though, since the correct values for 4.x and 5.x > > will still be different? > > Not if -pthread remains. In

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Kris Kennaway
On Wed, Sep 24, 2003 at 12:43:54PM +1000, John Birrell wrote: > On Tue, Sep 23, 2003 at 07:33:43PM -0700, Kris Kennaway wrote: > > Won't these ports still need to be fixed to look at > > PTHREAD_{LIBS,CFLAGS} though, since the correct values for 4.x and 5.x > > will still be different? > > Not if

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread John Birrell
On Tue, Sep 23, 2003 at 07:33:43PM -0700, Kris Kennaway wrote: > Won't these ports still need to be fixed to look at > PTHREAD_{LIBS,CFLAGS} though, since the correct values for 4.x and 5.x > will still be different? Not if -pthread remains. Internally gcc would link to a different library, but mo

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread Kris Kennaway
On Wed, Sep 24, 2003 at 12:32:05PM +1000, John Birrell wrote: > On Tue, Sep 23, 2003 at 07:18:21PM -0700, Kris Kennaway wrote: > > Here is a partial list of the ports that need to be taught to respect > > PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I > > just grepped for the

Re: Initial list of ports that fail due to -pthread

2003-09-23 Thread John Birrell
On Tue, Sep 23, 2003 at 07:18:21PM -0700, Kris Kennaway wrote: > Here is a partial list of the ports that need to be taught to respect > PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I > just grepped for the "-pthread is deprecated" error message). None of > these were fixed

Initial list of ports that fail due to -pthread

2003-09-23 Thread Kris Kennaway
Here is a partial list of the ports that need to be taught to respect PTHREAD_LIBS and PTHREAD_CFLAGS, from the latest 5.x package build (I just grepped for the "-pthread is deprecated" error message). None of these were fixed by ports/57047. It is likely that there are many more that also need t