Re: Fixing gcc 3.3 compile failures

Hi ! For games/inform just some escaped newlines: [ I already sent that to the maintainer, but then again to avoid double `work'... ] CUT --- veneer.c.orig Fri Jul 18 15:38:34 2003 +++ veneer.cFri Jul 18 15:39:44 2003 @@ -250,10 +250,10 @@ "#ifdef INFIX;if (obj has inf

Re: gcc-3.3 issues

Hi ! > Then configure runs gcc with wrong parameters. In GCC 3.3 -pedantic implies > -pedantic-error, unless -fpermissive is specified too. ??? The info page doesn't say so. If one can't trust the GNU info pages - what a mess, considered that they refuse to maintain proper manpages either... Con

Re: gcc-3.3 issues

Hi ! > What kind of enlightenment are you looking for? 0.17 e.g. 8-)) Seriously, I didn't mean to piss off anyone. Just wanted to learn about the *reason* of this incoherence. I apologize if the irony was way too masked. > gcc mailing list address is not secret, I suggest you to take it > the

Re: gcc-3.3 issues

Hi ! > http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/Warning-Options.html#Warning%20Options Hmm, that's exactly as in the info page. > http://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/C---Dialect-Options.html#C++%20Dialect%20Options > and search for permissive, to see the condition Alexander speaks of. W

Re: Fixing gcc 3.3 compile failures -- kde ports proposal

Hi ! Luckily the KDE ports are very uniform. Applying the obvious, trivial patch to configure always works on current. (Of course only since the patch utility is clever enough to try the hunk at different offsets...): --- configure.orig Sat Jul 19 16:54:39 2003 +++ configure Sat Jul 19 16:

Erratum: Re: Fixing gcc 3.3 compile failures -- kde ports proposal

Hi ! > With those settings, I could do a forced upgrade for everything. Ahem, not quite true, I forgot kdebase3. Everything configures, but that thing is the only reluctant to build. Some sort of known problem with static_cast as far as I can see. So - no portupgrade -fa on my current... *sigh

Re: Status of SCHED_ULE?

Hi ! > > I have a PS/2 mouse, I run -CURRENT from 2 days ago, and I experience the > > stuttering too. Me too, though I have to relativize this. My configuration is UP with a pentium 4, 2.4 GHz running gnome2, evolution, mozilla and some gnome-terminals. With 4BSD, the mouse cycles through non-r

Re: Status of SCHED_ULE?

Hi ! > I use the /dev/sysmouse and moused, not quite sure > why but that's how I've always used my mouse (PS2 or USB) with > FreeBSD. Could this have something to do with the mouse feeling > sloppy? Hmmm, I never used moused and always /dev/psm0 in X. Still experience the same thing. Cheers Pe

Re: Sched_Ule

Hi ! I have a Matrox G550. No DRI or other specials. PS/2 mouse. No moused. UP machine. The mouse stutters under compilation load (in X). I'll give moused a try and look whether the behaviour is the same on the console, but I doubt it. I suspect this thing is rendering related. Cheers Peter --

Re: More ULE bugs fixed.

Hi ! > Things should be much improved. Feedback, as always, is welcome. Wow ! Smoothly working under a load of approx. 4. Running gnome2, mozilla, evolution, mplayer and kpdf. Running portsdb -Uu and a kernel build. No stuttering mouse, no irritating delays, fast rendering. That's definitely bet

gcc-3.3 issues

Hi ! Some port builds bail out with errors. (Of course they do, that was expected.) This is definitely gcc-3.3 related. (They did build on 5.1-Release and do build on 4.8-Stable.) Would it be of interest for anyone to post them or is it way too early for that ? ('Wait until 5.2-Release is out ?

Re: gcc-3.3 issues

Hi ! > > s/gcc-3.3/ports/ issues and we are in agreement. alright, `port compile issues raised with the adoption of gcc-3.3' > > Patches to fix broken ports are welcome. Looking at AbiWord2 I suspect this has to be pushed upstream in some cases. OK, here is a - ahem - patch for aspell: --- prog/ch

Re: gcc-3.3 issues

Hi ! Sorry for that... That was my pre-get-rid-of-g++-workaround - how embarrassing ! Alexander pointed out in private (thank you), that this was a failure. > I am willing to test the patches if one of you have any. Try that instead: --- prog/checker_string.hpp.origTue Sep 24 03:34:52

Re: Fixing gcc 3.3 compile failures

OK, here is one for graphics/svgalib: --- src/vga.c.orig Fri Jul 18 13:27:40 2003 +++ src/vga.c Fri Jul 18 13:32:58 2003 @@ -3846,7 +3846,7 @@ #define ML_GETINT(x) \ ptr = strtok(NULL, " "); if(!ptr) break; \ - mmt.##x = atoi(ptr); + mmt.x = atoi(ptr);