Re: HEADS UP: GCC 3.2 in progress
Alexander Kabaev wrote: I will import GCC 3.2 snapshot from the top of FSF gcc-3_2-branch in about ten minutes. This task should not take long to complete, but since this is the first time I am doing it, there is good possibility of unexpected delays, so please be patient. Please respond immediately if you feel that I need to hold the import for some reason. Cool! Thank you for doing hard work, Alexander. BTW, does it mean that we just got a fresh new gcc maintainer? -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Maxim Sobolev wrote: Alexander Kabaev wrote: I will import GCC 3.2 snapshot from the top of FSF gcc-3_2-branch in about ten minutes. This task should not take long to complete, but since this is the first time I am doing it, there is good possibility of unexpected delays, so please be patient. Please respond immediately if you feel that I need to hold the import for some reason. Cool! Thank you for doing hard work, Alexander. BTW, does it mean that we just got a fresh new gcc maintainer? I just hope we didn't scare him too much :-) Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 10:21:13PM -0400, Joe Marcus Clarke wrote: Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again. This is really not that big of a deal. I'll just need to alter a patch, and update the Mozilla people. My understanding from watching the patches move through mozilla is that the next release of mozilla _will_ work correctly with -CURRENT because it is aware of us not using thunks. The thunks patch for -CURRENT was verified in the mozilla src tree a week or two back. -sc Correct. However, if the compiler changes in -CURRENT not to use thunks, then I need to adjust the local patch, and update the Mozilla bug. Our GCC 3.x now does the exact same thing GCC on Linux does. Why is this not a problem on Linux? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: GCC 3.2 in progress
I will import GCC 3.2 snapshot from the top of FSF gcc-3_2-branch in about ten minutes. This task should not take long to complete, but since this is the first time I am doing it, there is good possibility of unexpected delays, so please be patient. Please respond immediately if you feel that I need to hold the import for some reason. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
So, what is it about gcc 3.2 that's so important, considering that we wanted to do a real 5.0 release within 2 months? On Sun, 1 Sep 2002, Alexander Kabaev wrote: I will import GCC 3.2 snapshot from the top of FSF gcc-3_2-branch in about ten minutes. This task should not take long to complete, but since this is the first time I am doing it, there is good possibility of unexpected delays, so please be patient. Please respond immediately if you feel that I need to hold the import for some reason. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, 1 Sep 2002 14:34:12 -0700 (PDT) Matthew Jacob [EMAIL PROTECTED] wrote: So, what is it about gcc 3.2 that's so important, considering that we wanted to do a real 5.0 release within 2 months? Some well known problem present in our current GCC snapshot appear to be fixed in 3.2. GCC 3.2 is using vendor-independent C++ ABI. Assuming they got it right this time, this will allow us to upgrade to 3.3 more painlessly later. People who were asking for an upgrade got what they deserved :) -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 02:34:12PM -0700, Matthew Jacob wrote: So, what is it about gcc 3.2 that's so important, considering that we wanted to do a real 5.0 release within 2 months? This is really 3.1.1 -- so it is a minor point release. 3.2 fixes a bug that changes the API so it couldn't be fixed in 3.1.1. Otherwise they are the same compilers. That said, we don't want to be stuck with a stale compiler for all of 5.x. I highly recomend we use 3.3 in our 5.0-R. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Well, actually, I *wasn't* asking for an upgrade. From recent experience it is my estimation that a gcc upgrade sets 5.0 development back a month (that is, the last GCC upgrade kept *me* from working productively for around a month due to various this thats and the others). If that's what people want, that's fine. I could also be totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. This is, IMO, why FreeBSD is not going to be very successful. You cannot just make major toolchain changes w/o at least *some* belief that this is going to be done well. Did you do a dryrun with the import before checking things in? I don't mean to be hypercritical here, but I feel that it's fair, considering people are starting to really whine about how late 5.0 actually *is* at this point, to begin to ask not even the *hard* questions, but medium firm questions about gee, is this trip *really* necessary? -matt On Sun, 1 Sep 2002, Alexander Kabaev wrote: On Sun, 1 Sep 2002 14:34:12 -0700 (PDT) Matthew Jacob [EMAIL PROTECTED] wrote: So, what is it about gcc 3.2 that's so important, considering that we wanted to do a real 5.0 release within 2 months? Some well known problem present in our current GCC snapshot appear to be fixed in 3.2. GCC 3.2 is using vendor-independent C++ ABI. Assuming they got it right this time, this will allow us to upgrade to 3.3 more painlessly later. People who were asking for an upgrade got what they deserved :) -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, 1 Sep 2002, David O'Brien wrote: On Sun, Sep 01, 2002 at 02:34:12PM -0700, Matthew Jacob wrote: So, what is it about gcc 3.2 that's so important, considering that we wanted to do a real 5.0 release within 2 months? This is really 3.1.1 -- so it is a minor point release. 3.2 fixes a bug that changes the API so it couldn't be fixed in 3.1.1. Otherwise they are the same compilers. That said, we don't want to be stuck with a stale compiler for all of 5.x. I highly recomend we use 3.3 in our 5.0-R. All that's good, but is this on the roadmap of RE core so that adequate destabilization time is accounted for? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 02:50:50PM -0700, Matthew Jacob wrote: I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. This update has been *DEMANDED* in both -current and -ports for months now. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, 1 Sep 2002 14:50:50 -0700 (PDT) Matthew Jacob [EMAIL PROTECTED] wrote: From recent experience it is my estimation that a gcc upgrade sets 5.0 development back a month (that is, the last GCC upgrade kept *me* from working productively for around a month due to various this thats and the others). If that's what people want, that's fine. I could also be totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. Matt, the change was discussed several times on developers@, so this import is hardly 'out of nowhere'. This is, IMO, why FreeBSD is not going to be very successful. You cannot just make major toolchain changes w/o at least *some* belief that this is going to be done well. Did you do a dryrun with the import before checking things in? About five buildworlds on i386 and two on Alpha. Does that count as dry runs? -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Hi, totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. The 2.95.3 - 3.1 prerelease upgrade was a big step. 3.1 prerelease - 3.2 is a little step which fixes bugs, make kde working (gif support) again, fixes X11 and mozilla ports. I don't mean to be hypercritical here, but I feel that it's fair, considering people are starting to really whine about how late 5.0 actually *is* at this point, to begin to ask not even the *hard* questions, but medium firm questions about gee, is this trip *really* necessary? I think yes. Gcc 3.1 prerelease had some nasty bugs. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 02:56:26PM -0700, David O'Brien wrote: This update has been *DEMANDED* in both -current and -ports for months now. Yes, GCC 3.1 prerelease bites, big time, k thx. Better to fix it now than later, when people will actually expect it to work. I also dislike the apparent general policy of using prereleases for our compiler in FreeBSD. regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, 1 Sep 2002, Alexander Kabaev wrote: On Sun, 1 Sep 2002 14:50:50 -0700 (PDT) Matthew Jacob [EMAIL PROTECTED] wrote: From recent experience it is my estimation that a gcc upgrade sets 5.0 development back a month (that is, the last GCC upgrade kept *me* from working productively for around a month due to various this thats and the others). If that's what people want, that's fine. I could also be totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. Matt, the change was discussed several times on developers@, so this import is hardly 'out of nowhere'. I sure didn't see anything on the recent 5.0 schedule about this. Like I said- this is not meant to be hypercritical. Let's assume that I'm not paying that close attention, like a *lot* of developers to the flood of mail. There might have been a note about new compiler import on the recent 5.X schedule changes that surely would catch the eye. This is, IMO, why FreeBSD is not going to be very successful. You cannot just make major toolchain changes w/o at least *some* belief that this is going to be done well. Did you do a dryrun with the import before checking things in? About five buildworlds on i386 and two on Alpha. Does that count as dry runs? Surely they do. Did somebody in ia64 sparc ppc get a headsup? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
I should note that I'm raising more of a flag than normal. This would have been a firing offense at several companies I've worked at. It's not unreasonable to take a lesson from *why* these things are firing offenses and start to raise queries. I've done so. Duty is done. Go back to sleep. On Mon, 2 Sep 2002, Martin Blapp wrote: Hi, totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. The 2.95.3 - 3.1 prerelease upgrade was a big step. 3.1 prerelease - 3.2 is a little step which fixes bugs, make kde working (gif support) again, fixes X11 and mozilla ports. I don't mean to be hypercritical here, but I feel that it's fair, considering people are starting to really whine about how late 5.0 actually *is* at this point, to begin to ask not even the *hard* questions, but medium firm questions about gee, is this trip *really* necessary? I think yes. Gcc 3.1 prerelease had some nasty bugs. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 03:00:34PM -0700, Will Andrews wrote: On Sun, Sep 01, 2002 at 02:56:26PM -0700, David O'Brien wrote: This update has been *DEMANDED* in both -current and -ports for months now. Yes, GCC 3.1 prerelease bites, big time, k thx. Better to fix it now than later, when people will actually expect it to work. I also dislike the apparent general policy of using prereleases for our compiler in FreeBSD. This is the same as using RELENG_4_6 (ie, 4.6-SECURE) in something. We get bug fixes (that must work on *all* supported GCC arches). The risk is _well_ mitigated. Why is everyone second guessing Kan on this import??? It will be a wonder if we get another import done by him. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Matthew Jacob wrote: This would have been a firing offense at several companies I've worked at. It's not unreasonable to take a lesson from *why* these things are firing offenses and start to raise queries. I've done so. Duty is done. Go back to sleep. Would you rather that we ship with a known broken prerelease compiler? Would you rather that we changed from 3.1-prerelease to 3.1.1-release? gcc-3.2 *is* 'gcc-3.1.1 + ABI bugfix'. They renamed the 3.1 branch to 3.2. All future 3.1.x releases will be called 3.2.x. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
These arguments are all quite familiar- I'm not really moved one way or the other. The point here is that major changes need to be very visible on a product's schedule. You can argue that it isn't a major change- but I'd assert that any toolchain change *is* a major change. I'm *not* arguing against the change- I don't know nearly enough to have an opinion. I *am* commenting on how major changes coming in with little notice often add substantial delays. Furthermore, lack of putting such changes up in such a fashion that a folks in distributed development environment can then adequately plan/protect themselves so *their* stuff is protected is also an issue. Look- if Alexander hadn't said anything, I *probably* wouldn't have noticed. However, he felt that this was important enough to tease people with a 10 minutes until the bombs start falling mail message. It's not unreasonable to raise this as an issue. Or if you think it *is* unreasonable, we can go offline so I can discuss it. -matt On Sun, 1 Sep 2002, Peter Wemm wrote: Matthew Jacob wrote: This would have been a firing offense at several companies I've worked at. It's not unreasonable to take a lesson from *why* these things are firing offenses and start to raise queries. I've done so. Duty is done. Go back to sleep. Would you rather that we ship with a known broken prerelease compiler? Would you rather that we changed from 3.1-prerelease to 3.1.1-release? gcc-3.2 *is* 'gcc-3.1.1 + ABI bugfix'. They renamed the 3.1 branch to 3.2. All future 3.1.x releases will be called 3.2.x. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Matthew Jacob wrote: The point here is that major changes need to be very visible on a product's schedule. You can argue that it isn't a major change- but I'd assert that any toolchain change *is* a major change. re@ have been practically begging for it. I'm *not* arguing against the change- I don't know nearly enough to have an opinion. I *am* commenting on how major changes coming in with little notice often add substantial delays. Furthermore, lack of putting such changes up in such a fashion that a folks in distributed development environment can then adequately plan/protect themselves so *their* stuff is protected is also an issue. Look- if Alexander hadn't said anything, I *probably* wouldn't have noticed. However, he felt that this was important enough to tease people with a 10 minutes until the bombs start falling mail message. It's not unreasonable to raise this as an issue. Umm. Are you reading your -developers mail? === begin quote === Subject: Re: A plea for a 5.0-RELEASE .. From: Alexander Kabaev [EMAIL PROTECTED] Date: Sat, 31 Aug 2002 23:26:09 -0400 (20:26 PDT) To: [EMAIL PROTECTED] On Sat, 31 Aug 2002 20:19:11 -0400 (EDT) Robert Watson [EMAIL PROTECTED] wrote: If we can manage it, we also need a compiler upgrade for the base system. Right now we can't build usable gif support in QT with the base system g++, we have to install a port. I am testing a buildworld with GCC 3.2 after Heimdal upgrade. If nothing goes wrong, I plan to import GCC 3.2 tomorrow. My home machine is running kernel/buildworld compiled with 3.2 already. === end quote === And then there was quite a bit of followup about it. It has already been established that everybody wanted it, and that it has been tested on i386 and alpha, and the sparc64 folks want it very badly too. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 03:23:58PM -0700, David O'Brien wrote: This is the same as using RELENG_4_6 (ie, 4.6-SECURE) in something. We get bug fixes (that must work on *all* supported GCC arches). The risk is _well_ mitigated. Why is everyone second guessing Kan on this import??? It will be a wonder if we get another import done by him. Oh, I think GCC 3.2.1 prerelease knocks the socks off 3.1 prerelease. But any time someone is using a FreeBSD -RELEASE, gcc -v should say release in it. That's just MHO. Part of the reason I say this is because the gcc31 port uses the release version and is not subject to the same bugs that the *prerelease* 3.1 compiler that was in -CURRENT was. regards, -- wca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Mon, 2 Sep 2002, Martin Blapp wrote: Hi, totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. The 2.95.3 - 3.1 prerelease upgrade was a big step. 3.1 prerelease - 3.2 is a little step which fixes bugs, make kde working (gif support) again, fixes X11 and mozilla ports. Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again. This is really not that big of a deal. I'll just need to alter a patch, and update the Mozilla people. Joe I don't mean to be hypercritical here, but I feel that it's fair, considering people are starting to really whine about how late 5.0 actually *is* at this point, to begin to ask not even the *hard* questions, but medium firm questions about gee, is this trip *really* necessary? I think yes. Gcc 3.1 prerelease had some nasty bugs. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Umm. Are you reading your -developers mail? Yes, as best as I can. But I didn't see a GCC 3.2 import on anyone's bullet list. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, 1 Sep 2002 18:52:04 -0400 (EDT) Joe Marcus Clarke [EMAIL PROTECTED] wrote: Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again. This is really not that big of a deal. I'll just need to alter a patch, and update the Mozilla people. Joe Why would that change? I do not remember me switching thunks off. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, 1 Sep 2002, Alexander Kabaev wrote: On Sun, 1 Sep 2002 18:52:04 -0400 (EDT) Joe Marcus Clarke [EMAIL PROTECTED] wrote: Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again. This is really not that big of a deal. I'll just need to alter a patch, and update the Mozilla people. Joe Why would that change? I do not remember me switching thunks off. I have no idea if it changed or not. This was just an observation. I'll be testing Mozilla with gcc-3.2.1, and I will fix things as necessary. But thanks for the info. Joe -- Alexander Kabaev PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 03:51:52PM -0700, Matthew Jacob wrote: Umm. Are you reading your -developers mail? Yes, as best as I can. But I didn't see a GCC 3.2 import on anyone's bullet list. To quote Robert Watson: My list basically consists of: General - GEOM as default storage management on all platforms, related dependencies - Switch in sysinstall to easily turn on ufs2 - Final resolution of any perl removal related problems - rcNG as the default boot mechanism - New gcc? Matt, please stop trolling. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Yes, as best as I can. But I didn't see a GCC 3.2 import on anyone's bullet list. To quote Robert Watson: My list basically consists of: General - GEOM as default storage management on all platforms, related dependencies - Switch in sysinstall to easily turn on ufs2 - Final resolution of any perl removal related problems - rcNG as the default boot mechanism - New gcc? Small bullet item. Matt, please stop trolling. That is an offensive assumption. It wasn't trolling- nor was it intended as such. Argh. Why do I bother? Screw it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Totally off-topic for this thread, sorry. On Sun, Sep 01, 2002 at 04:58:54PM -0600, Scott Long wrote: To quote Robert Watson: My list basically consists of: General - GEOM as default storage management on all platforms, related dependencies Note: I have tried bringing to -current's attention several times that GEOM and md(4) do not play well together. The following fstab entry continues to fail: /dev/md0 /tmp md rw,nosuid,nodev,-s=32m,-p=1777 0 0 Fyi, -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Matthew Jacob wrote: Yes, as best as I can. But I didn't see a GCC 3.2 import on anyone's bullet list. To quote Robert Watson: My list basically consists of: General - GEOM as default storage management on all platforms, related dependencies - Switch in sysinstall to easily turn on ufs2 - Final resolution of any perl removal related problems - rcNG as the default boot mechanism - New gcc? Small bullet item. Alexander is new at working within our operation so we should give him some room to get fully up to speed. I'm glad that somebody other than me is dealing with this. :-) We really did need this to be done before 5.0-R as the gcc prerelease was a bit of a showstopper when it cannot compile a whole bunch of 'must have' packages. (eg: KDE etc) Lets say that developer awareness of the pending import should have been dealt with better and chalk it up as a learning experience. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Matthew Jacob wrote: Yes, as best as I can. But I didn't see a GCC 3.2 import on anyone's bullet list. To quote Robert Watson: My list basically consists of: General - GEOM as default storage management on all platforms, related dependencies - Switch in sysinstall to easily turn on ufs2 - Final resolution of any perl removal related problems - rcNG as the default boot mechanism - New gcc? Small bullet item. Alexander is new at working within our operation so we should give him some room to get fully up to speed. I'm glad that somebody other than me is dealing with this. :-) We really did need this to be done before 5.0-R as the gcc prerelease was a bit of a showstopper when it cannot compile a whole bunch of 'must have' packages. (eg: KDE etc) Lets say that developer awareness of the pending import should have been dealt with better and chalk it up as a learning experience. Of course. And being accused of 'trolling' is also a learning experience. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Of course. And being accused of 'trolling' is also a learning experience. I would have to agree with your sarcasm, seems like there is a big troll hunt and everyone is being accused. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
Hey lets find a way to keep this goddamned thread going.. huh can we... yeah... please... I love hitting delete!!! Keep it up and we'll be as cool as [EMAIL PROTECTED] ... /sarcasm On Sunday, September 1, 2002, at 07:12 PM, Matthew Jacob wrote: Matthew Jacob wrote: Yes, as best as I can. But I didn't see a GCC 3.2 import on anyone's bullet list. To quote Robert Watson: My list basically consists of: General - GEOM as default storage management on all platforms, related dependencies - Switch in sysinstall to easily turn on ufs2 - Final resolution of any perl removal related problems - rcNG as the default boot mechanism - New gcc? Small bullet item. Alexander is new at working within our operation so we should give him some room to get fully up to speed. I'm glad that somebody other than me is dealing with this. :-) We really did need this to be done before 5.0-R as the gcc prerelease was a bit of a showstopper when it cannot compile a whole bunch of 'must have' packages. (eg: KDE etc) Lets say that developer awareness of the pending import should have been dealt with better and chalk it up as a learning experience. Of course. And being accused of 'trolling' is also a learning experience. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sunday, September 1, 2002, at 07:14 PM, David W. Chapman Jr. wrote: Of course. And being accused of 'trolling' is also a learning experience. I would have to agree with your sarcasm, seems like there is a big troll hunt and everyone is being accused. I wouldn't call it trolling but I would call it stretching the bounds of being on topic. The accusation was unfair however the amount of exchange on the topic [and off] may have gotten out of hand. This tends to irritate people. Dave -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, Sep 01, 2002 at 05:12:43PM -0700, Matthew Jacob wrote: [...] Of course. And being accused of 'trolling' is also a learning experience. Ok, I apologize for calling you a 'troll'. I certainly didn't mean it in the context of what's going on in other mailing lists, and it probably wasn't appropriate in any context. Please note, hovever, that many of the concerns that you've brought up in this thread have been *heavily* discussed in the public mailing list over the past month. Just two weeks ago there was a heated discussion over whether to import gcc 3.2, or leapfrog it and wait for 3.3. There have been many more discussions like it. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
On Sun, 1 Sep 2002, Sean Chittenden wrote: totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. The 2.95.3 - 3.1 prerelease upgrade was a big step. 3.1 prerelease - 3.2 is a little step which fixes bugs, make kde working (gif support) again, fixes X11 and mozilla ports. Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again. This is really not that big of a deal. I'll just need to alter a patch, and update the Mozilla people. My understanding from watching the patches move through mozilla is that the next release of mozilla _will_ work correctly with -CURRENT because it is aware of us not using thunks. The thunks patch for -CURRENT was verified in the mozilla src tree a week or two back. -sc Correct. However, if the compiler changes in -CURRENT not to use thunks, then I need to adjust the local patch, and update the Mozilla bug. However, it sounds like this isn't the case. Joe -- Sean Chittenden PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: GCC 3.2 in progress
totally wrong, and this won't break things. I'm just a bit startled that this appears out of nowhere (I sure don't recall it being discussed) and just happens, with 10 minutes warning. The 2.95.3 - 3.1 prerelease upgrade was a big step. 3.1 prerelease - 3.2 is a little step which fixes bugs, make kde working (gif support) again, fixes X11 and mozilla ports. Actually, if 3.2 doesn't use thunks, it's likely to break Mozilla again. This is really not that big of a deal. I'll just need to alter a patch, and update the Mozilla people. My understanding from watching the patches move through mozilla is that the next release of mozilla _will_ work correctly with -CURRENT because it is aware of us not using thunks. The thunks patch for -CURRENT was verified in the mozilla src tree a week or two back. -sc -- Sean Chittenden msg42429/pgp0.pgp Description: PGP signature
Re: HEADS UP: GCC 3.2 in progress
Thank you. Let's move on. On Sun, 1 Sep 2002, Scott Long wrote: On Sun, Sep 01, 2002 at 05:12:43PM -0700, Matthew Jacob wrote: [...] Of course. And being accused of 'trolling' is also a learning experience. Ok, I apologize for calling you a 'troll'. I certainly didn't mean it in the context of what's going on in other mailing lists, and it probably wasn't appropriate in any context. Please note, hovever, that many of the concerns that you've brought up in this thread have been *heavily* discussed in the public mailing list over the past month. Just two weeks ago there was a heated discussion over whether to import gcc 3.2, or leapfrog it and wait for 3.3. There have been many more discussions like it. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
