Date: Sun, 1 Sep 2002 22:21:13 -0400 (EDT) From: Joe Marcus Clarke <marcus@marcuscom.com> To: Sean Chittenden <sean@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: HEADS UP: GCC 3.2 in progress Message-ID: <20020901222018.X8348-100000@shumai.marcuscom.com> In-Reply-To: <20020902021050.GE61993@ninja1.internal>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020901222018.X8348-100000>