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 better than _4BSD. (UP machine) Cheers Peter -- [EMAIL PROTECTED] Campus der Max-Planck-Institute Tübingen Netzwerk- und Systemadministration Tel: +49 7071 601 598 Fax: +49 7071 601 616 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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 -- [EMAIL PROTECTED] Campus der Max-Planck-Institute Tübingen Netzwerk- und Systemadministration Tel: +49 7071 601 598 Fax: +49 7071 601 616 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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 Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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-responding, jumping and smoothly sliding under compilation load. Whereas under ULE, it is sort of constantly stuttering. On the other hand I experienced satisfactory responsiveness even under a load of 4, one of the most irritating exceptions being the stuttering mouse (though with 4BSD, responsiveness is beyond all hope...) There is another exception which is far more frustrating. Using vi (or view) on a file and typing 'j' on the last line. It'll take approximately half a second per line scrolling by. (Still talking of compilation load here.) Cheers Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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* Cheers Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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. Well, here it is: -fpermissive Downgrade messages about nonconformant code from errors to warnings. By default, G++ effectively sets -pedantic-errors without -pedantic; this option reverses that. This behavior and this option are superseded by -pedantic, which works as it does for GNU C. I admit, I'm not a native speaker, so please correct me. Doesn't that mean, if you don't specify any pedantic, it defaults to -pedantic-errors for C++, but if you specify -pedantic, you don't get errors for warnings like it should be... ?? Cheers Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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:55:37 2003
@@ -4236,7 +4236,7 @@
CXXFLAGS=-ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE
-Wcast-align -Wconversion $CXXFLAGS
;;
esac
-CXXFLAGS=-Wall -pedantic -W -Wpointer-arith
-Wmissing-prototypes -Wwrite-strings $CXXFLAGS
+CXXFLAGS=-Wall -pedantic -fpermissive -W -Wpointer-arith
-Wmissing-prototypes -Wwrite-strings $CXXFLAGS
echo $as_me:$LINENO: checking whether $CXX supports -Wundef 5
echo $ECHO_N checking whether $CXX supports -Wundef... $ECHO_C 6
(Beware of newlines when doing cut-and-paste).
But that would break things on non-current.
So how about setting a variable in /etc/make.conf ?
I think for the time being this is not too much for
a current-user...
MY_CXX_BAILS_OUT_ON_KDE_CONFIGURE=yo
(It needn't be so long though ;-)
Then put that patch in the files directory as - e.g. -
`current-patch-configure'.
And change the ports Makefile along the lines of
the following patch for koffice:
--- Makefile.orig Sat Jul 19 21:48:15 2003
+++ MakefileSat Jul 19 21:49:34 2003
@@ -38,4 +38,9 @@
.include ${.CURDIR}/../../x11/kde3/Makefile.kde
+.ifdef MY_CXX_BAILS_OUT_ON_KDE_CONFIGURE
+pre-configure:
+ cd ${WRKSRC} patch ${FILESDIR}/current-patch-configure
+.endif
+
.include bsd.port.mk
With those settings, I could do a forced upgrade for everything.
I know this can't be the clean, now-we-all-are-happy-solution.
But as I already mentioned - for the time being...
Cheers
Peter
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
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);
ML_GETINT(HDisplay);
ML_GETINT(HSyncStart);
Just abused concatenation...
But I'm pretty sure that the following is
what was intended, thusly the better patch:
--- src/vga.c.orig Fri Jul 18 13:27:40 2003
+++ src/vga.c Fri Jul 18 13:34:38 2003
@@ -3845,8 +3845,9 @@
mmt.pixelClock = atof(ptr) * 1000;
#define ML_GETINT(x) \
- ptr = strtok(NULL, ); if(!ptr) break; \
- mmt.##x = atoi(ptr);
+ do { ptr = strtok(NULL, ); if(!ptr) break; \
+ mmt.x = atoi(ptr); } \
+ while (0)
ML_GETINT(HDisplay);
ML_GETINT(HSyncStart);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
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 infix__watching) n=1;#endif;\
#ifdef DEBUG;if (debug_flag 1 ~= 0) n=1;#endif;\
if (n==1) {\
- #ifdef DEBUG;n=debug_flag 1;
+ #ifdef DEBUG;n=debug_flag 1;\
debug_flag=debug_flag-n;#endif;\
print \[ ~\, (name) obj, \~.\, (property) id, \(\;\
- switch(y) { 1: print a; 2: print a,\,\,b; 3: print
+ switch(y) { 1: print a; 2: print a,\,\,b; 3: print \
a,\,\,b,\,\,c;\
4: print a,\,\,b,\,\,c,\,\,d;\
5: print a,\,\,b,\,\,c,\,\,d,\,\,e;\
CUT
Cheers
Peter
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
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... Confused. Please enlighten me. Cheers Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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 there if you feel so inclined. See above. Wading though merge conflicts in texi files after each import is hardly my idea of fun, but I will not stop you for trying :) Well, how much worse is that compared to a `mergemaster -i' orgy from a 4.2 to a 4.8 ? Ugh, don't, no, let me be, argh... Sidestep: I *love* to see that my CPUTYPE=p4 is not downgraded anymore. Cheers Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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/checker_string.hpp.origTue Sep 24 03:34:52 2002 +++ prog/checker_string.hpp Thu Jul 17 20:02:58 2003 @@ -5,6 +5,7 @@ // it at http://www.gnu.org/. #include stdio.h +#include g++/cassert #include aspell.h It works on my colleague's and my current and my stable. But maybe it's not the right way (tm) (to 'do-it) :-) But should I post that on -ports, -current or send it to the ports maintainer ? I'd rather avoid tracking -ports... Is something like this expected, i.e., certain combinations of -W* and -pedantic to produce errors when they didn't before? Yes, though -ansi and -pedantic are not that troublesome I think. A real killer is -Werror. But -W* is not the only source of compile errors - see above. Cheers Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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 2002 +++ prog/checker_string.hpp Thu Jul 17 22:37:38 2003 @@ -5,6 +5,7 @@ // it at http://www.gnu.org/. #include stdio.h +#include assert.h #include aspell.h And *please* don't ask why I didn't use assert.h in the first place. *flush* Cheers anyway Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
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 ?')
Cheers
Peter
--
[EMAIL PROTECTED]
Netzwerk- und Systemadministration
Campus der Max-Planck-Institute Tübingen
Tel: +49 7071 601598
Fax: +49 7071 601616
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
