Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-11 Thread Alexander Leidinger
On Wed, 10 Sep 2003 12:41:41 -0400 Michael Edenfield <[EMAIL PROTECTED]> wrote: > Err, not quite. Tried to build gnome2 lately? :) > > gnome2 depends on gnomemedia2. > gnomemedia2 depends on gstreamer-plugins. > gstreamer-plugins fails because ARTSD_FLAGS in several dozen Makefiles > includes -

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Steve Kargl
On Thu, Sep 11, 2003 at 01:41:05AM +0200, Michael Nottebrock wrote: > Steve Kargl wrote: > > >Why? The portmgr can tag the ports collection at any point in > >time before or after the -pthread deprecation date. > > Steve, ports-freeze dates are set and published ahead of time just as dates > fo

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Michael Nottebrock
Daniel Eischen wrote: I feel that a FreeBSD that manages to break so many existing configure-scripts and build systems is degraded in usefulness. Please, this is -current. If you want less pain then stick with -stable and you won't be annoyed by the -pthread removal. Perhaps I should make it clea

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Michael Nottebrock
Steve Kargl wrote: Why? The portmgr can tag the ports collection at any point in time before or after the -pthread deprecation date. Steve, ports-freeze dates are set and published ahead of time just as dates for releases are. It's obviously not a good thing to have to try and be very conservat

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Daniel Eischen
On Wed, 10 Sep 2003, Michael Edenfield wrote: > * David O'Brien <[EMAIL PROTECTED]> [030910 15:33]: > > On Wed, Sep 10, 2003 at 12:41:41PM -0400, Michael Edenfield wrote: > > > gnome2 depends on gnomemedia2. > > > gnomemedia2 depends on gstreamer-plugins. > > > gstreamer-plugins fails because ARTS

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Michael Edenfield
* David O'Brien <[EMAIL PROTECTED]> [030910 15:33]: > On Wed, Sep 10, 2003 at 12:41:41PM -0400, Michael Edenfield wrote: > > gnome2 depends on gnomemedia2. > > gnomemedia2 depends on gstreamer-plugins. > > gstreamer-plugins fails because ARTSD_FLAGS in several dozen Makefiles > > includes -pthread.

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Daniel Eischen
On Wed, 10 Sep 2003, Michael Nottebrock wrote: > Sorry if this sounds a bit flame-ish, but the way I see it we now have a > system compiler in -CURRENT that doesn't even compile a hello world if > -pedantic is specified and breaks with lots of existing software out there > that tries to use a threa

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread David O'Brien
On Wed, Sep 10, 2003 at 09:56:45AM -0700, Steve Kargl wrote: > > >4.9 and 5.0-R are independent branch. By your logic we should wait to > > >4.10 or 4.11 or 4.12 or ... before any substantial change can be made > > >to -CURRENT. > > > > The point is that is isn't wise to commit a change like the

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread David O'Brien
On Wed, Sep 10, 2003 at 12:41:41PM -0400, Michael Edenfield wrote: > gnome2 depends on gnomemedia2. > gnomemedia2 depends on gstreamer-plugins. > gstreamer-plugins fails because ARTSD_FLAGS in several dozen Makefiles > includes -pthread. This is being worked on from the compiler stand point. _

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Steve Kargl
On Wed, Sep 10, 2003 at 05:23:55PM +0200, Michael Nottebrock wrote: > Steve Kargl wrote: > > >I have no problems in building the traditional C "hello world" > >program with "cc -pedantic". > > You're right about that, you'll need a C++ hello world (, cout). > This is in the archives anyway and (

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Michael Edenfield
* Alexander Leidinger <[EMAIL PROTECTED]> [030910 10:53]: > In 5-current we have 3 threads libraries and want to be able to install > and use them in parallel. So there has to be a way to specify which one. > This is why we need the ports collection to respect the PTHREAD* > variables. A lot of po

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Martin
Am Mi, 2003-09-10 um 15.30 schrieb Michael Nottebrock: > Sorry if this sounds a bit flame-ish, but the way I see it we now have a > system compiler in -CURRENT that doesn't even compile a hello world if > -pedantic is specified and breaks with lots of existing software out there Yes. I agree on th

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Michael Nottebrock
Steve Kargl wrote: I have no problems in building the traditional C "hello world" program with "cc -pedantic". You're right about that, you'll need a C++ hello world (, cout). This is in the archives anyway and (should be) well known. (why could this change not have been made _after_ 4.9 is out

Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Alexander Leidinger
On Wed, 10 Sep 2003 15:30:28 +0200 Michael Nottebrock <[EMAIL PROTECTED]> wrote: > Sorry if this sounds a bit flame-ish, but the way I see it we now have > a system compiler in -CURRENT that doesn't even compile a hello world > if-pedantic is specified and breaks with lots of existing software out

Quo vadis, -CURRENT? (recent changes to cc & compatibility)

2003-09-10 Thread Michael Nottebrock
Sorry if this sounds a bit flame-ish, but the way I see it we now have a system compiler in -CURRENT that doesn't even compile a hello world if -pedantic is specified and breaks with lots of existing software out there that tries to use a threads library because -pthread errors out (why could this