Re: buildworld error: rm: tar: is a directory
>>>>> eculp writes: > Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>: > | On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote: > | > I'm having problems with current buildworld in gnu now on two different > | > machines in current(today). The latest is the following: > | > > | > rm: tar: is a directory > | > *** Error code 1 > | > > | > Stop in /usr/src/gnu/usr.bin/tar. > | > *** Error code 1 > | > > | > Stop in /usr/src/gnu/usr.bin/tar. > | > *** Error code 1 > | > > | > Stop in /usr/src/gnu/usr.bin. > | > *** Error code 1 > | > > | > I'm begining to wonder if I'm getting a complete checkout with cvsup > | > of the gnu tree. > | > > | ``rm -rf /usr/obj/usr/src/gnu/usr.bin/tar'' and try again. > Ruslan > That didn't seem to work. I've erased the /usr/obj/usr tree several > times and even gnu but without luck. After resuping getting the > error doing a rm -rf /usr/obj/usr/src/gnu/usr.bin/tar and then > another make buildworld, I continue to get: Try 'cvs update -PdA' Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger [EMAIL PROTECTED] [KeyID: 400B38E9] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: timeseal program doesn't work with FreeBSD-5.1
>>>>> Juan Francisco Rodriguez Hervella writes: > Hello: > I usuallly play chess on FICS. They use a programme > called "Timeseal", which is pre-compiled for a lot > of different platforms (Linux, Windows, FreeBSD, etc). > This program adjust clocks when network delay appears > or something like that, I'm not an expert on the subject. > The problem is that this program use to work on FreeBSD-4.X > but it's not working any longer with FreeBSD-5.0 The Linux version (timeseal.Linux-2.0.29-i386) should work. Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger [EMAIL PROTECTED] [KeyID: 400B38E9] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sh dies w/ sig 12
>>>>> Seth Hettich writes: > Trying to update to -current, in SU mode, doing the make installworld: > [ ! -e /usr/bin/passwd ] || echo foo > will make sh die > This is even with the "new" sh from my buildworld (I am running the new > kernel). > Ideas? I think this was discussed in -current some time ago. Compile a -current kernel and reboot. Then redo the make installworld. Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger [EMAIL PROTECTED] [KeyID: 400B38E9] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
make world breakage
Sources updated yesterday: ===> sbin/mountd cc -O -pipe -DNFS -DMFS -DCD9660 -DMSDOSFS -c /usr/src/sbin/mountd/mountd.c /usr/src/sbin/mountd/mountd.c:164: warning: `struct xucred' declared inside parameter list /usr/src/sbin/mountd/mountd.c:164: warning: its scope is only this definition or declaration, which is probably not what you want. /usr/src/sbin/mountd/mountd.c:166: warning: `struct xucred' declared inside parameter list /usr/src/sbin/mountd/mountd.c:187: warning: `struct xucred' declared inside parameter list /usr/src/sbin/mountd/mountd.c:205: variable `def_anon' has initializer but incomplete type /usr/src/sbin/mountd/mountd.c:206: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:206: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:207: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:207: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:208: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:208: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:209: extra brace group at end of initializer /usr/src/sbin/mountd/mountd.c:209: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:209: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:209: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c:211: warning: excess elements in struct initializer /usr/src/sbin/mountd/mountd.c:211: warning: (near initialization for `def_anon') /usr/src/sbin/mountd/mountd.c: In function `get_exportlist': /usr/src/sbin/mountd/mountd.c:736: storage size of `anon' isn't known /usr/src/sbin/mountd/mountd.c: In function `do_opt': /usr/src/sbin/mountd/mountd.c:1337: argument `cr' doesn't match prototype /usr/src/sbin/mountd/mountd.c:166: prototype declaration /usr/src/sbin/mountd/mountd.c:1376: warning: passing arg 2 of `parsecred' from incompatible pointer type /usr/src/sbin/mountd/mountd.c: In function `do_mount': /usr/src/sbin/mountd/mountd.c:1599: argument `anoncrp' doesn't match prototype /usr/src/sbin/mountd/mountd.c:164: prototype declaration /usr/src/sbin/mountd/mountd.c:1618: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c: In function `parsecred': /usr/src/sbin/mountd/mountd.c:1847: argument `cr' doesn't match prototype /usr/src/sbin/mountd/mountd.c:187: prototype declaration /usr/src/sbin/mountd/mountd.c:1858: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1859: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1860: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1878: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1885: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1886: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1888: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1896: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1898: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1903: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1904: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1907: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1907: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1913: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1913: dereferencing pointer to incomplete type /usr/src/sbin/mountd/mountd.c:1916: dereferencing pointer to incomplete type *** Error code 1 Stop in /usr/src/sbin/mountd. *** Error code 1 Jean-Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: x11/XFree86-4
>>>>> Stephan van Beerschoten writes: > I am having trouble compiling XFree86 from the ports tree.. I once > ever few weeks recompile several packages again because I run -CURRENT > and want to keep everything nicely sync'ed and updated in ports too.. > But while compiling .. I got this error: > LD_LIBRARY_PATH=../../exports/lib cc -o appres -ansi -pedantic -Dasm=__asm -Wal > l -Wpointer-arith -L../../exports/lib appres.o -lXt -lSM -lICE -lXext -lX11 > -L/usr/X11R6/lib -Wl,-rpath,/usr/X11R6/lib > ../../exports/lib/libXt.so: undefined reference to `pthread_cond_signal' Don't compile with CFLAGS=-O3 or above. -O or -O2 is OK. Jean-Marc -- Jean-Marc Zucconi -- PGP Key: finger [EMAIL PROTECTED] [KeyID: 400B38E9] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can someone explain this?
>>>>> Bruce Evans writes: > The default of 4 for -mpreferred-stack-boundary perfectly preserves > any initial misaligment of the stack. Under FreeBSD the stack is > initially misaligned (for doubles) with a probability of 1/2. There > was some discussion of fixing this when gcc-2.95 was imported, but > nothing was committed. I use the following local hack: > diff -c2 kern_exec.c~ kern_exec.c > *** kern_exec.c~ Mon May 1 15:56:40 2000 > --- kern_exec.c Mon May 1 15:56:42 2000 > *** > *** 627,630 > --- 647,659 > vectp = (char **) > (destp - (imgp->argc + imgp->envc + 2) * sizeof(char*)); > + > +/* > + * Align stack to a multiple of 0x20. > + * XXX vectp has the wrong type; we usually want a vm_offset_t; > + * the suword() family takes a void *, but should take a vm_offset_t. > + * XXX should align stack for signals too. > + * XXX should do this more machine/compiler-independently. > + */ > +vectp = (char **)(((vm_offset_t)vectp & ~(vm_offset_t)0x1F) - 4); > /* Any chance that your fix be committed? :-) The impact of misalignments on performance is considerable. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can someone explain this?
>>>>> Dan Nelson writes: > In the last episode (May 05), Jean-Marc Zucconi said: >> Here is something I don't understand: >> >> $ sh -c '/usr/bin/time ./a.out' >> 2.40 real 2.38 user 0.01 sys >> $ /usr/bin/time ./a.out >> 7.19 real 7.19 user 0.00 sys >> >> The same program is 3 times slower in the second case. The effect is >> systematic but depends on the program being run. I have seen inverse >> behavior with another program. Using time -l, I note that this seems >> to be related with a higher value of 'involuntary context switches' >> (3 times more switches in the slower case). > It has to do with your stack. Calling the program via /bin/sh sets up > your environment differently, so your program's stack starts at a > different place. Try running this: > main (int argc, char **argv) > { > int i; > double x=2, y=2, z=2; > printf ("%p\n",&i); > for (i = 0; i < 1000; i++) z = y*x; > return 0; > } > Run this commandline: > STR= ; export STR ; while : ; do ; STR=z$STR ; /usr/bin/time ./a,out ; done > And watch your execution time flip flop every 4 runs. OK. The effect is indeed very clear. > Here are some bits from the gcc infopage explaining your options if you > want consistant speed from programs using doubles: > `-mpreferred-stack-boundary=NUM' > Attempt to keep the stack boundary aligned to a 2 raised to NUM > byte boundary. If `-mpreferred-stack-boundary' is not specified, > the default is 4 (16 bytes or 128 bits). > The stack is required to be aligned on a 4 byte boundary. On > Pentium and PentiumPro, `double' and `long double' values should be > aligned to an 8 byte boundary (see `-malign-double') or suffer > significant run time performance penalties. On Pentium III, the > Streaming SIMD Extention (SSE) data type `__m128' suffers similar > penalties if it is not 16 byte aligned. > `-mno-align-double' > Control whether GCC aligns `double', `long double', and `long > long' variables on a two word boundary or a one word boundary. > Aligning `double' variables on a two word boundary will produce > code that runs somewhat faster on a `Pentium' at the expense of > more memory. > *Warning:* if you use the `-malign-double' switch, structures > containing the above types will be aligned differently than the > published application binary interface specifications for the 386. Now the problem is that the -mpreferred-stack-boundary=NUM option does not solve the problem :-( I still get a penalty in 50% of the cases. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Can someone explain this?
Here is something I don't understand: $ sh -c '/usr/bin/time ./a.out' 2.40 real 2.38 user 0.01 sys $ /usr/bin/time ./a.out 7.19 real 7.19 user 0.00 sys The same program is 3 times slower in the second case. The effect is systematic but depends on the program being run. I have seen inverse behavior with another program. Using time -l, I note that this seems to be related with a higher value of 'involuntary context switches' (3 times more switches in the slower case). Running -current (SMP) Here is my test program: main () { int i; double x, y, z; for (i = 0; i < 1; i++) z = y*x; } Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: port/XFree86-4 make install fail.
>>>>> Idea Receiver writes: > "make all" success without any problem. There was an error but "make all" always complete. > however, make install fail ;( What are your CFLAGS in /etc/make.conf ? Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86-4 can't start
>>>>> Nawfal M Rouyan writes: > Hi, > I've installed XFree86 version 4 trough the ports > collection > but it won't start and I think it is because of the > missing mouse module. Since I'm using lynx, I can't > attached the /var/log/XFree86.0.log file for your > reference. I can only paste the error I found in the Yes, the mouse drive was not built :-(. TRy again with the following patch to scripts/configure Jean-Marc Index: scripts/configure === RCS file: /home/ncvs/ports/x11/XFree86-4/scripts/configure,v retrieving revision 1.58 diff -u -r1.58 configure --- scripts/configure 2000/03/11 00:20:34 1.58 +++ scripts/configure 2000/03/12 00:23:57 @@ -196,7 +196,7 @@ echo "#undef BuildXInputExt" >> $F echo "#define BuildXInputExt NO" >> $F else - echo "#define XInputDrivers dynapro elo2300 elographics magellan microtouch \ + echo "#define XInputDrivers mouse dynapro elo2300 elographics magellan microtouch \ mutouch spaceorb wacom" >> $F # XXX broken in 3.9.18 # if [ X${MACHINE} != X"alpha" ]; then -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
>>>>> David O'Brien writes: >> rename it libstdc++.so.1. Then you just have to modify your executable >> so that it looks for libstdc++.so.1 instead of libstdc++.so.3 > Why not just reinstall the problematic executables? Because I don't always have the time to recompile. My (temporary) solution is invaluable when I am in a hurry. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Loader.rc: unknown command
Hi, With a new installed world I get this message at boot: > \ Loader.rc Loader.rc: unknown command Fortunately this does not prevent the machine to boot :-) Any clue? Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new C++ compiler changes
>>>>> Louis A Mamakos writes: > I just put a new -current on my test machine, and watched a bunch of stuff > fall over and die due to the new C++ implementation. > Is it possible to bump the revision of libstdc++ (and perhaps others) so > that existing programs can continue to function? I fear I will be > tracking down occasional broken C++ programs for days now. The solution I adopted is to keep the old libstdc++.so.3 and rename it libstdc++.so.1. Then you just have to modify your executable so that it looks for libstdc++.so.1 instead of libstdc++.so.3 (script below :-)) Jean-Marc #!/usr/bin/perl if (!$ARGV[0] || $ARGV[0] eq "-h") { print STDERR "usage: $0 file...\n"; exit 1; } foreach (@ARGV) { if (! -f $_) { print STDERR "$_: not found\n"; } else { ($s) = `file $_`; if ($s !~ /: ELF.*dynamically linked/) { print STDERR "$_: bad format\n$s"; } else { @h = `objdump -h $_`; $done = 0; foreach $s (@h) { if ($s =~ /dynstr/) { &edit ($_, $s); $done = 1; } } if (!$done) { print STDERR "$_: no .dynstr section\n"; } } } } sub edit { $f = shift; $_ = shift; split; $len = hex ($_[2]); $skip = hex ($_[5]); if (!open (F, $f)) { print STDERR "$f: $!\n"; return; } $n = sysread (F, $a, $skip); if ($n != $skip) { print STDERR "$f: short read\n"; return; } $n = sysread (F, $_, $len); if ($n != $len) { print STDERR "$f: short read\n"; return; } if (! /libstdc\+\+.so.3/) { print STDERR "$f: libstdc++.so.3 not used\n"; return; } s/libstdc\+\+.so.3/libstdc++.so.1/; if (!open (G, ">$f.1")) { print STDERR "can't create $f.1\n"; close F; return; } syswrite (G, $a, $skip); syswrite (G, $_, $len); while ($n != 0) { $n = sysread (F, $_, 10); if ($n < 0) { print STDERR "$f: read error\n"; close F; close G; return; } if ($n != 0) { $w = syswrite (G, $_, $n); if ($n < $w) { print STDERR "$f.1: write error\n"; close F; close G; return; } } } close F; close G; system ("mv $f $f.backup && mv $f.1 $f"); } -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Netscape and -current
This happens with a kernel/world from today: netscape is unusable. Most of the time it freezes after a few seconds. Here is the tail of kdump: 484 communicator-4.7 RET select 0 484 communicator-4.7 CALL old.sigprocmask(0x1,0) 484 communicator-4.7 RET old.sigprocmask 0 484 communicator-4.7 CALL gettimeofday(0xbfbfb874,0) 484 communicator-4.7 RET gettimeofday 0 484 communicator-4.7 CALL old.sigprocmask(0x3,0) 484 communicator-4.7 RET old.sigprocmask 0 484 communicator-4.7 CALL old.sigprocmask(0x1,0x2000) 484 communicator-4.7 RET old.sigprocmask 0 484 communicator-4.7 CALL select(0xa,0x50011f48,0,0x50011f08,0x50011efc) 484 communicator-4.7 RET select 0 484 communicator-4.7 CALL gettimeofday(0x50011dac,0) 484 communicator-4.7 RET gettimeofday 0 484 communicator-4.7 CALL old.sigprocmask(0x3,0) 484 communicator-4.7 RET old.sigprocmask 8192/0x2000 484 communicator-4.7 CALL gettimeofday(0x50011f60,0) 484 communicator-4.7 RET gettimeofday 0 484 communicator-4.7 PSIG SIGALRM caught handler=0x8fea40 mask=0x0 code=0x0 484 communicator-4.7 CALL sigreturn(0x50011ed4) 484 communicator-4.7 RET sigreturn -1 errno 14 Bad address Any idea? Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh bug
>>>>> Martin Cracauer writes: >> Today I encountered again the problem when doing `man MIME::*' (you >> have to install /usr/ports/mail/p5-MIME-Tools). Curiously, I have no >> problem with `man \*' >> Again reverting to eval.c r1.22 solve the problem. > I can now reproduce the problem. Please test the appended diff which > should fix this problem while still working for the > here-backquote-three-stage-pipeline case. Thanks for the patch. It fixes the problem (definitively I hope :-)) here. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh bug
>>>>> Steve Price writes: > On Mon, 8 Nov 1999, Jean-Marc Zucconi wrote: > # >>>>> Jean-Marc Zucconi writes: > # > # > Try this in -current > # > $ cat some_file | head > # > # > I have to use ^C to regain control. > # > # ... and reverting to rev. 1.22 of eval.c fixes the problem. > Does revision 1.24 work? I told you that it worked, but in fact it does not :-) Today I encountered again the problem when doing `man MIME::*' (you have to install /usr/ports/mail/p5-MIME-Tools). Curiously, I have no problem with `man \*' Again reverting to eval.c r1.22 solve the problem. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh bug
>>>>> Steve Price writes: > On Mon, 8 Nov 1999, Jean-Marc Zucconi wrote: > # >>>>> Jean-Marc Zucconi writes: > # > # > Try this in -current > # > $ cat some_file | head > # > # > I have to use ^C to regain control. > # > # ... and reverting to rev. 1.22 of eval.c fixes the problem. > Does revision 1.24 work? Yes. It works too. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sh bug
>>>>> Jean-Marc Zucconi writes: > Try this in -current > $ cat some_file | head > I have to use ^C to regain control. ... and reverting to rev. 1.22 of eval.c fixes the problem. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sh bug
Try this in -current $ cat some_file | head I have to use ^C to regain control. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic in -current (trap 12)
This is with a current kernel - a kernel built 2 days ago runs ok. The system crashes at boot, just after the disk checks. I don't have a core dump, only the message printed on screen: fault code: supervisor read , page not present instruction pointer: 0xc0175396 from my kernel: c0175234 t vfs_setdirty c0175360 T getblk c01756f8 T geteblk c017573c T allocbuf This is on a SMP/softupdates system. Jean-Marc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Mmap problem in -current?
I just noticed (kernel&world from friday) that locate always cores dump: $ locate xxx Segmentation fault (core dumped) $ gdb -c locate.core /usr/bin/locate Program terminated with signal 11, Segmentation fault. (gdb) bt #0 0x804964b in ___tolower () #1 0x235000 in ?? () #2 0x8049166 in ___tolower () #3 0x8048f93 in ___tolower () #4 0x80489f5 in ___tolower () The problem disappears if I recompile locate without the -DMMAP option. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger j...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 xsetpointer causes silo overflows (Was: Re: Fixed my MAMEd sio problem.)
>>>>> David Dawes writes: > IMHO the problem is in the joystick driver and in your assumptions. By > configuring the joystick in your Xserver config file, you're giving the > server exclusive use of the device for the lifetime of the X server > process. Implementing more agressive closing might solve your particular > problem, but it doesn't deal with the real problem of the joystick driver > causing the silo overflows. All interrupts are blocked when you read the joystick position, and this is the reason of the silo overflows. It is almost impossible to avoid (it could be possible to use a very high frequency timer and to check the joystick status during the interrupts, but this has an impact on the precision of the position). However keeping the device opened can't cause silo overflows. It seems rather than the X server continues to read the joystick position after the client stops using it. This can be considered as a bug in the X server. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger j...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
booting kernel without wd0
Hi, Today, I can't boot my new kernel. I get: changing device to wd0a can't open /dev/rwdo0: device not configured My system is 100% scsi, and wdc0 is disabled in my config file: config kernel root on da0 dumps on da0 ... controller wdc0at isa? disable port IO_WD1 irq 14 My previous kernel (april, 29) boots fine. Is there a fix? Jean-Marc -- Jean-Marc ZucconiPGP Key: finger j...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: ctm-mail cvs-cur.5292.gz 18/82
>>>>> Stephen McKay writes: > I also did not receive part 18. Are the individual parts kept anywhere > for anonymous ftp access? I will put it on http://www.freebsd.org/~jmz/part18 in a few minutes. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger j...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
ctm-mail cvs-cur.5292.gz 18/82
This one did not arrive in my mailbox. Can someone send it to me? I would like to avoid downloading 6Mbytes again. Jean-Marc To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: make world failure
>>>>> Mark Murray writes: > "David O'Brien" wrote: >> On Thu, Apr 29, 1999 at 03:19:37AM +0200, Jean-Marc Zucconi wrote: >> > I just encountered this: >> > >> > ===> gnu/usr.bin/cc/doc >> > makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I >> > /u3/ > src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I > /u3/src/gn > u/usr.bin/cc/doc -I /u3/src/gnu/usr.bin/cc/doc > /u3/src/gnu/usr.bin/cc/doc/../.. > /../../contrib/egcs/gcc/gcc.texi -o gcc.info >> >> As latest egcs committer, info docs are out of my forte. Hopefully >> someone knowledgeable about them can help you out. > Best chance is a total resup followed by a source-tree de-turd. I find > that _two_ "make cleandir"'s followed by "cd /usr/obj;" > does a good job even if it is a bit of overkill. It appears that this was a cvs problem: my update log showed: ... cvs update: Updating contrib/egcs/gcc cvs update: move away contrib/egcs/gcc/invoke.texi; it is in the way C contrib/egcs/gcc/invoke.texi I removed the file and did a 'cvs update -PdA' again and this solved the problem. Jean-Marc -- Jean-Marc ZucconiPGP Key: finger j...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
make world failure
I just encountered this: ===> gnu/usr.bin/cc/doc makeinfo -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc -I /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/cp --no-split -I /u3/src/gnu/usr.bin/cc/doc -I /u3/src/gnu/usr.bin/cc/doc /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi -o gcc.info /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:434: Next reference to nonexistent node `Invoking G++'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi:2085: Cross reference to nonexistent node `Warning Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/gcc.texi:1619: Cross reference to nonexistent node `Optimize Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/extend.texi:2236: Cross reference to nonexistent node `C++ Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:431: Menu reference to nonexistent node `Target Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:429: Menu reference to nonexistent node `Directory Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:428: Menu reference to nonexistent node `Link Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:427: Menu reference to nonexistent node `Assembler Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:425: Menu reference to nonexistent node `Preprocessor Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:424: Menu reference to nonexistent node `Optimize Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:423: Menu reference to nonexistent node `Debugging Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:422: Menu reference to nonexistent node `Warning Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:421: Menu reference to nonexistent node `C++ Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:420: Menu reference to nonexistent node `C Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:401: Cross reference to nonexistent node `Code Gen Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:208: Cross reference to nonexistent node `Submodel Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:202: Cross reference to nonexistent node `Target Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:195: Cross reference to nonexistent node `Directory Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:185: Cross reference to nonexistent node `Link Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:179: Cross reference to nonexistent node `Assembler Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:166: Cross reference to nonexistent node `Preprocessor Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:147: Cross reference to nonexistent node `Optimize Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:136: Cross reference to nonexistent node `Debugging Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:115: Cross reference to nonexistent node `Warning Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:103: Cross reference to nonexistent node `C++ Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:94: Cross reference to nonexistent node `C Dialect Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:77: Menu reference to nonexistent node `Running Protoize'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:76: Menu reference to nonexistent node `Environment Variables'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:74: Menu reference to nonexistent node `Code Gen Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:72: Menu reference to nonexistent node `Submodel Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:71: Menu reference to nonexistent node `Target Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:69: Menu reference to nonexistent node `Directory Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:68: Menu reference to nonexistent node `Link Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:67: Menu reference to nonexistent node `Assembler Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:65: Menu reference to nonexistent node `Preprocessor Options'. /u3/src/gnu/usr.bin/cc/doc/../../../../contrib/egcs/gcc/invoke.texi:64: Menu reference to nonexistent node `Optimize Options'. /u3/src/gnu