Wake on PCI enabled by FreeBSD?
Hello, I was a bit stalked this morning by finding that my computer had tunrned itself on 5-10 minutes after I turned it off to go to bed last night :) I turned off, and it turned itself back on again. I have turned off most wake up events in the BIOS, but Wake on PCI is set to AUTO, meaning that the operating system decides wether this should be enabled or not. I have both a ISDN card (Asuscom 128 PCI, iwic driver) and a Ethernet card (3COM 590, xl driver) that could be triggered to wake up the computer. But this has never happened before, so I guess some changes (ACPI?) has caused FreeBSD to enable this feature. Anyone know anything about this? I'm running an HP Vei8, PII 400 MHz box and FreeBSD-CURRENT built one or two days ago. Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
src/gnu/usr.bin/tar source code deleted?
src/gnu/usr.bin/tar source code deleted? Makefile can't find *.c *.h files very funny what is wrong??? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: src/gnu/usr.bin/tar source code deleted?
Andres A Moya wrote: src/gnu/usr.bin/tar source code deleted? Makefile can't find *.c *.h files very funny what is wrong??? Tar sources now live in src/contrib/tar. make(1) should be able to find those sources using .PATH: directive in Makefile. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mergemaster broken?
On Tue, Jun 04, 2002 at 10:42:35PM -0700, Kris Kennaway wrote: On Tue, Jun 04, 2002 at 07:52:19PM -0700, walt wrote: Aha! After doing 'use.perl port' it works again, thanks. Looks like this is going to be necessary after each buildworld, then. :-/ I thought that's what NO_PERL is for. And speaking of NO_PERL... any reference to this knob was removed from share/examples/etc/make.conf 1.888. JMA -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
libncurses cannot show the first column on the screen
Hi all, The libncurses commit on May 21 seems not working properly. I cvsupped latest current ports, build a typical ncurses app (lynx) and find that the first column is not shown correctly. Bascially it is blank on the first column. I have rebuilt libncurses before May 21's commit and the problem disappeared. Has anyone got the same problem in -current? I have tried both the console and login via Linux. All have the same problem. Below is a copy of what was seen on the screen by lynx .cshrc. If the message is not wrapped, you can notice that the first column is blank. (p1 of 2) $FreeBSD: src/share/skel/dot.cshrc,v 1.13 2001/01/10 17:35:28 archie Exp $ .cshrc - csh resource script, read at beginning of execution by each shell see also csh(1), environ(7). lias h history 25 lias j jobs -l lias lals -a lias lfls -FA lias llls -lA A righteous umask mask 22 et path = (/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin /usr/local bin /usr/X11R6/bin $HOME/bin) etenv EDITOR vi - press space for next page -- Arrow keys: Up and Down to move. Right to follow a link; Left to go back. H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: src/gnu/usr.bin/tar source code deleted?
On Wed, Jun 05, 2002 at 11:45:24AM +, Andres A Moya wrote: src/gnu/usr.bin/tar source code deleted? Yes, see the cvs logs. Makefile can't find *.c *.h files very funny what is wrong??? You have stale .depend files? Kris msg39192/pgp0.pgp Description: PGP signature
Re: My postgresql7 not working for new gcc
--- Alfred Perlstein [EMAIL PROTECTED] wrote: Getting a traceback to both us (FreeBSD) and the Postgresql developers would be very helpful. Alfred, Today, I rebuilt -current postgresql with latest cvsup, the core dump did not occurred. However, I still have to specify WITHOUT_SSL=yes. Otherwise, the ports stop during configuration as shown below. === Configuring for postgresql-7.2.1_1 loading cache ./config.cache checking host system type... i386-portbld-freebsd5.0 checking which template to use... freebsd checking whether to build with locale support... yes checking whether to build with recode support... no checking whether to build with multibyte character support... yes, default SQL_ASCII checking whether NLS is wanted... no checking for default port number... 5432 checking for default soft limit on number of connections... 32 checking for gcc... cc checking whether the C compiler (cc -O -pipe -march=pentiumpro ) works... yes checking whether the C compiler (cc -O -pipe -march=pentiumpro ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether cc accepts -g... yes using CFLAGS=-O -pipe -march=pentiumpro checking whether the C compiler (cc -O -pipe -march=pentiumpro ) works... yes checking whether the C compiler (cc -O -pipe -march=pentiumpro ) is a cross-compiler... no checking for Cygwin environment... no checking for mingw32 environment... no checking for executable suffix... no checking how to run the C preprocessor... cc -E checking whether cc needs -traditional... no checking whether to build with Tcl... no checking whether to build with Tk... no checking whether to build Perl modules... no checking whether to build Python modules... no checking whether to build Java/JDBC tools... no checking whether to build with PAM support... no building with OpenSSL support checking whether to build the ODBC driver... no checking whether to build C++ modules... yes checking for c++... c++ checking whether the C++ compiler (c++ -O -pipe -march=pentiumpro ) works... yes checking whether the C++ compiler (c++ -O -pipe -march=pentiumpro ) is a cross-compiler... no checking whether we are using GNU C++... yes checking whether c++ accepts -g... yes using CXXFLAGS= -O -pipe -march=pentiumpro checking how to run the C++ preprocessor... c++ -E checking for string... yes checking for namespace std in C++... yes using CPPFLAGS= -I/usr/local/include -I/usr/include using LDFLAGS= -L/usr/lib checking for mawk... no checking for gawk... gawk checking for flex... /usr/bin/flex checking whether ln -s works... yes checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for ranlib... ranlib checking for lorder... lorder checking for tar... /usr/bin/tar checking for bison... bison -y checking for perl... /usr/bin/perl checking for readline... yes (-lreadline) checking for library containing using_history... none required checking for main in -lbsd... no checking for setproctitle in -lutil... yes checking for main in -lm... yes checking for main in -ldl... no checking for main in -lsocket... no checking for main in -lnsl... no checking for main in -lipc... no checking for main in -lIPC... no checking for main in -llc... no checking for main in -ldld... no checking for main in -lld... no checking for main in -lcompat... yes checking for main in -lBSD... no checking for main in -lgen... no checking for main in -lPW... no checking for main in -lresolv... no checking for main in -lunix... no checking for library containing crypt... -lcrypt checking for __inet_ntoa in -lbind... no checking for inflate in -lz... yes checking for library containing fdatasync... no checking for CRYPTO_new_ex_data in -lcrypto... yes checking for SSL_library_init in -lssl... yes checking for crypt.h... no checking for dld.h... no checking for endian.h... no checking for fp_class.h... no checking for getopt.h... no checking for ieeefp.h... no checking for pwd.h... no checking for sys/ipc.h... no checking for sys/pstat.h... no checking for sys/select.h... no checking for sys/sem.h... no checking for sys/socket.h... no checking for sys/shm.h... no checking for sys/types.h... no checking for sys/un.h... no checking for termios.h... no checking for kernel/OS.h... no checking for kernel/image.h... no checking for SupportDefs.h... no checking for netinet/in.h... no checking for netinet/tcp.h... no checking whether string.h and strings.h may both be included... no checking for readline/readline.h... no checking for readline.h... no checking for readline/history.h... no checking for history.h... no checking for openssl/ssl.h... no configure: error: header file openssl/ssl.h is required for OpenSSL __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha boot1 UFS support: HELP NEEDED!
Somebody who has an alpha at hand needs to make the alpha boot1 code use sys/boot/common/ufsread.c before June 19th where the UFS2 patch is scheduled to be committed. I have no idea how much or how little work this is. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha boot1 UFS support: HELP NEEDED!
On Wed, Jun 05, 2002 at 02:15:49PM +0200, Poul-Henning Kamp wrote: Somebody who has an alpha at hand needs to make the alpha boot1 code use sys/boot/common/ufsread.c before June 19th where the UFS2 patch is scheduled to be committed. I'll take a look into this during the next WE. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Please test the UFS2 patch!
I have uploaded an updated version of the UFS2 patch: http://phk.freebsd.dk/patch/ufs2.patch Please test this! Neither Kirk nor I have heard very much feedback, so absent any reports of total disaster, it will be committed around 19th of june. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
More on NO_PERL and make.conf
In another thread on mergemaster the subject of the NOPERL flag for make.conf came up. The flag NOPERL is added to make.conf automatically by the script 'use.perl port'. BUT, note that /usr/src/usr.bin/Makefile looks for the flag NO_PERL instead of NOPERL, and so that is the reason mergmaster wound up broken ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mergemaster broken?
On 05 Jun 2002 15:01:24 +0200, Dag-Erling Smorgrav wrote: Looks like this is going to be necessary after each buildworld, then. :-/ No. Mergemaster should not use Perl, and the fact that it does is a bug. That's probably an overstatement. Perl used to be in the base system, and was, at the time an easy way to stat() a file. I'd say mergemaster's use of perl is use of an obsoleted interface at worst. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Please test the UFS2 patch!
On Wed, 05 Jun 2002 15:13:28 +0200, Poul-Henning Kamp wrote: I have uploaded an updated version of the UFS2 patch: http://phk.freebsd.dk/patch/ufs2.patch Please test this! Is this something we can drop in and expect to work / panic / corrupt our filesystems without any change in the way we interact with our systems? If not, where is the information on things we'll have to change in the way we interact with our systems? It's not in this URL, and earlier test requests sounded scarier than this one, so I didn't pay attention to the instructions they included. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Please test the UFS2 patch!
In message [EMAIL PROTECTED], Sheldon Hearn writes: On Wed, 05 Jun 2002 15:13:28 +0200, Poul-Henning Kamp wrote: I have uploaded an updated version of the UFS2 patch: http://phk.freebsd.dk/patch/ufs2.patch Please test this! Is this something we can drop in and expect to work / panic / corrupt our filesystems without any change in the way we interact with our systems? Yes, if you just drop it in, nothing should change much after all. You can then create ufs2 filesystems with newfs -O 2 and start to beat up the new code for good. Bug reports to kirk@ and phk@ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Please test the UFS2 patch!
+---[ Poul-Henning Kamp ]-- | | Yes, if you just drop it in, nothing should change much after all. | | You can then create ufs2 filesystems with newfs -O 2 and start to | beat up the new code for good. Is it helpful to test this via md type mounts, or only on physical media right now? -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | M:+61 416 022 411 | ACN: 082 081 472 ABN: 83 082 081 472 |[EMAIL PROTECTED]| Carpe Daemon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Please test the UFS2 patch!
In message [EMAIL PROTECTED], Andrew Kenneth Milton write s: +---[ Poul-Henning Kamp ]-- | | Yes, if you just drop it in, nothing should change much after all. | | You can then create ufs2 filesystems with newfs -O 2 and start to | beat up the new code for good. Is it helpful to test this via md type mounts, or only on physical media right now? Any testing is helpful, no matter how its done, but of course if you can think of some way to test it which nobody else does, it will be much more interesting. There are many tests of that sort you can do with md(4) mounts, for instance beating on dump/restore... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: libncurses cannot show the first column on the screen
In the last episode (Jun 05), Shizuka Kudo said: Hi all, The libncurses commit on May 21 seems not working properly. I cvsupped latest current ports, build a typical ncurses app (lynx) and find that the first column is not shown correctly. Bascially it is blank on the first column. I have rebuilt libncurses before May 21's commit and the problem disappeared. I sent a comment to the maintainer last week about this, who replied he was a bit busy but would get to it soon. He hasn't, so I'll poke him again. :) It seems to only affect lynx from what I have seen. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Safe to go to -CURRENT?
I've been monitoring the -CURRENT mailing list for about a day or two, and haven't seen anything that's really broken (except for GCC 3.x, which I don't use anyway). So, is it safe to upgrade to -CURRENT yet? TIA for the info, Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[Fwd: Safe to go to -CURRENT?]
I've been monitoring the -CURRENT mailing list for about a day or two, and haven't seen anything that's really broken (except for GCC 3.x, which I don't use anyway). So, is it safe to upgrade to -CURRENT yet? TIA for the info, Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Safe to go to -CURRENT?
On Wed, Jun 05, 2002 at 08:46:59AM +, Christopher Nehren wrote: I've been monitoring the -CURRENT mailing list for about a day or two, and haven't seen anything that's really broken (except for GCC 3.x, which I don't use anyway). So, is it safe to upgrade to -CURRENT yet? TIA for the info, What do you do with the system? It is fairly difficult to make any recommendation without some info about what the system does. For example, is this a production box? -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
buildworld error in gnu/lib/libstdc++
Hi all, I've been seeing a compile error in gnu/lib/libstdc++ for days now. Since no one else reported it (not even tinderbox) I can only wonder what's up, and expecially how to get out of this. The only thing peculiar to this machine is that I've cleared up everything which predated GCC 3.1; so I have no libstdc++ installed, no old includes, etc. Anyway, I am attaching the error (it's extremely long). I already did - make clean make clean make cleandir - rm -rf /usr/obj and more obvious attempts at fixing this, but still no change. Any suggestion? Is this local breakage or ...? Bye, Andrea -- I believe the technical term is Oops! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
buildworld failure in libfetch
I'm trying to upgrade from a 2002.05.10-CURRENT, with a fresh cvsup. Error attached. Regards, -- Michael Nottebrock --- error Description: application/java-vm
ps seems broken
Yeah, I know about kernel world being out of sync; that ought not be the case, as I just finished the usual buildworld, kernel, installworld, mergemaster sequence. For further evidence: g1-9(5.0-C)[1] uname -a ls -lio `which ps` file `which ps` FreeBSD g1-9.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Wed Jun 5 09:34:03 PDT 2002 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W i386 15995 -r-xr-xr-x 1 root wheel - 398740 Jun 5 09:52 /bin/ps /bin/ps: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped g1-9(5.0-C)[2] ps -ax ps: pid tt state time command: keyword not found ps: no valid keywords g1-9(5.0-C)[3] CVSup was started at 0347 hrs. PDT against cvsup14.freebsd.org; had finished by 0355 hrs. PDT. More details available on that score should they prove of interest. I'll poke around see if I can see what's broken, but thought that mentioning this might be of use. Cheers, david -- David H. Wolfskill [EMAIL PROTECTED] Trying to support or use Microsoft products makes about as much sense as painting the outside of a house with watercolors. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ps seems broken
* From David Wolfskill [EMAIL PROTECTED] Yeah, I know about kernel world being out of sync; that ought not be the case, as I just finished the usual buildworld, kernel, installworld, mergemaster sequence. For further evidence: g1-9(5.0-C)[1] uname -a ls -lio `which ps` file `which ps` FreeBSD g1-9.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Wed Jun 5 09:34:03 PDT 2002 [EMAIL PROTECTED]:/common/S3/obj/usr/src/sys/LAPTOP_30W i386 15995 -r-xr-xr-x 1 root wheel - 398740 Jun 5 09:52 /bin/ps /bin/ps: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped g1-9(5.0-C)[2] ps -ax ps: pid tt state time command: keyword not found ps: no valid keywords g1-9(5.0-C)[3] This is due to me un-breaking seperation of keywords and not testing enough. Sorry. Give me five minutes. CVSup was started at 0347 hrs. PDT against cvsup14.freebsd.org; had finished by 0355 hrs. PDT. More details available on that score should they prove of interest. I'll poke around see if I can see what's broken, but thought that mentioning this might be of use. Cheers, david -- David H. Wolfskill[EMAIL PROTECTED] Trying to support or use Microsoft products makes about as much sense as painting the outside of a house with watercolors. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- J. Mallett [EMAIL PROTECTED]FreeBSD: The Power To Serve I've coined new words, like, misunderstanding and Hispanically. -- George W. Bush, Radio-Television Correspondents Association dinner, Washington, D.C., March 29, 2001 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failure in libfetch
Michael Nottebrock wrote: Error attached. Correctly this time. Regards, -- Michael Nottebrock === lib/libfetch cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/fetch.c -o fetch.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/common.c -o common.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/ftp.c -o ftp.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wp ointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/http.c -o http.o cc -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized - c /usr/src/lib/libfetch/file.c -o file.o building static fetch library ranlib libfetch.a cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/fetch.c -o fetch.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/common.c -o common.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/ftp.c -o ftp.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/http.c -o http.So cc -fpic -DPIC -O -pipe -march=athlon -I. -DINET6 -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-unin itialized -c /usr/src/lib/libfetch/file.c -o file.So make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libssl.a. Stop
Re: buildworld failure in libfetch
David Wolfskill wrote: Were you running with -j ? 'cause the error appears to be with libssl, not libfetch. Nope. And I built OK, both with -j8 (on 2x866 PII) -j4 (on laptop), though I didn't use the athlon specification I tried unsetting CPUTYPE, no change. You might try a combination of no -j clearing /usr/obj/usr/src to see if you can make it recur in a pristine environment. I rm -rf /usr/obj before every build. Regards, -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failure in libfetch
If memory serves me right, Michael Nottebrock wrote: David Wolfskill wrote: Were you running with -j ? 'cause the error appears to be with libssl, not libfetch. Nope. I've seen this too, starting with a pristine /usr/obj and no -j option. I wonder if this has to do with the recent SSL support added to libfetch? Bruce. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing perl usage from mergemaster
[ I'm replacing -hackers with -arch for reasons that are clear below. ] On Thu, 6 Jun 2002, Giorgos Keramidas wrote: Hello dougb all, Here's a patch that removes all trails of Perl usage from mergemaster. Your work looks good, but I wish you'd asked before embarking on it. My current plan is actually to import netbsd's stat(1), which will solve this problem very neatly. I was hoping to do it sooner than now, but some family business, and a dead hard drive interfered with that plan. I am reasonably sure that I can get to it tonight. NetBSD's stat(1) is very feature rich, compiles cleanly on -current, and handled all the stuff I threw at it in semi-rigorous testing. I can't imagine anyone objecting to the import, but here's your chance. Meanwhile, my apologies to those -current users who've been inconvenienced somewhate ironic considering my enthusiastic campaigning to get rid of perl in the base. Mea culpa. Doug -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing perl usage from mergemaster
On 2002-06-05 15:27 -0700, Doug Barton wrote: On Thu, 6 Jun 2002, Giorgos Keramidas wrote: Hello dougb all, Here's a patch that removes all trails of Perl usage from mergemaster. Your work looks good, but I wish you'd asked before embarking on it. My current plan is actually to import netbsd's stat(1), which will solve this problem very neatly. I was hoping to do it sooner than now, but some family business, and a dead hard drive interfered with that plan. I am reasonably sure that I can get to it tonight. Nevermind. Nobody's pushing things. Whenever you feel like it, and stat's on its way to our tree, let me know if I can help with mergemaster the removal of perl. NetBSD's stat(1) is very feature rich, compiles cleanly on -current, and handled all the stuff I threw at it in semi-rigorous testing. I can't imagine anyone objecting to the import, but here's your chance. Nah. No direct src/ stuff for me, except for the occasional manpage fix. I'll probably wait until NetBSD's stat is imported, and retry. In the meantime, I'll try to test NetBSD's stat, or even come up with a few regression tests for NetBSD's stat. jmallett seems to like adding such things to our tree. Then perhaps, after stat is tested, we can re-hack mergemaster ;) Giorgos. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing perl usage from mergemaster
Doug Barton wrote: On Thu, 6 Jun 2002, Giorgos Keramidas wrote: Here's a patch that removes all trails of Perl usage from mergemaster. Your work looks good, but I wish you'd asked before embarking on it. My current plan is actually to import netbsd's stat(1), which will solve this problem very neatly. I was hoping to do it sooner than now, but some family business, and a dead hard drive interfered with that plan. I am reasonably sure that I can get to it tonight. If all it did was motivate you to do the patch sooner than you would have, then it was worthwhile. ;^). If on the other hand, you want to wait so that you aren't rushed, there's really no reason to not commit his code in the interim, as an interim fix that you will later replace with stat(1). Either way, it's all nice work. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I can not compile the kernel
--
root@juanillo:/usr/src/sys/i386/compile/JUANILLO $ make
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I.
-I../../.. -I../../../dev -I../../../contrib/dev/acpica
-I../../../contrib/ipfilter -I../../../../include -D_KERNEL
-ffreestanding -include opt_global.h -fno-common
-mpreferred-stack-boundary=2 -Werror ../../../i386/i386/locore.s
{standard input}: Assembler messages:
{standard input}:1689: Warning: rest of line ignored; first ignored
character is `t'
{standard input}:1691: Error: unknown pseudo-op: `.'
{standard input}:1806: Error: missing ')'
{standard input}:1806: Error: missing ')'
{standard input}:1806: Error: junk `tmpstk)- 0xc000)' after expression
*** Error code 1
Stop in /usr/src/sys/i386/compile/JUANILLO.
---
After a CVSUP on 18:13 EST, the problem still exists. I'd fix it myself,
except that I have no idea how it's even arriving at line 1689 (since
the file referenced doesn't even have 1100 lines). I've CVSUP'd numerous
times, and the error remains. I'm surprised no one else has brought this
up yet -- is it not affecting anyone else?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: ps seems broken
On Wed, Jun 05, 2002 at 10:24:07AM -0700, J. Mallett wrote: * From David Wolfskill [EMAIL PROTECTED] [snip] g1-9(5.0-C)[2] ps -ax ps: pid tt state time command: keyword not found ps: no valid keywords g1-9(5.0-C)[3] This is due to me un-breaking seperation of keywords and not testing enough. Sorry. Give me five minutes. Hi, may I ask you what kind of changes are you doing to ps ? since I've worked a lot on ps to make it SUSV3 complian and don't want to redo all the job I've done. some days ago, I've asked to be recorded to the `FreeBSD C99 POSIX Conformance Project' (http://www.FreeBSD.org/projects/c99/) as the ps maintainer but the page has not been updated yet. Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
dump (via amanda) causing panics
For the last week or so I've had my laptop panic every time amanda did a dump of it. This happens with a kernel as of yesterday so it probably wasn't just a bad update. Before the crash I see the following in dmesg: ad0: count 6359632 size transfers not supported bus_dmamap_load: Too many segs! buf_len = 0xc204abb0 ad0: READ command tiemotu tag=0 serv=0 - resetting ad0: resetting devices .. done [the above repeated twice more] ad0: count 6359632 size transfers not supported bus_dmamap_load: Too many segs! buf_len = 0xc204abb0 ad0: READ command tiemotu tag=0 serv=0 - resetting ad0: trying to fall back to PIO mode ad0: resetting devices .. done ad0: count 6359632 size transfers not supported PANIC I don't have a stack trace at the moment because I didn't have my kernel compiled with -gstabs+. I'm working on that. Dump does seem to run for a while before the panic occurs and I was able to dump / to /dev/null without a panic. Any ideas? -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg39219/pgp0.pgp Description: PGP signature
Re: mergemaster broken?
walt [EMAIL PROTECTED] writes: Looks like this is going to be necessary after each buildworld, then. :-/ No. Mergemaster should not use Perl, and the fact that it does is a bug. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- === gnu/usr.bin/cc/cc_int ... /d/home/des/tinderbox/src/contrib/gcc/config/i386/i386.c:54:2: warning: #warning NEED TO REVISIT PIC_REG_USED AND -mprofiler-epilogue SUPPORT === gnu/usr.bin/cc/cc /d/home/des/tinderbox/src/contrib/gcc/gcc.c: In function `process_command': /d/home/des/tinderbox/src/contrib/gcc/gcc.c:3335: warning: passing arg 4 of `getobjformat' from incompatible pointer type /d/home/des/tinderbox/src/contrib/gcc/gcc.c:3377: warning: assignment discards qualifiers from pointer target type /d/home/des/tinderbox/src/contrib/gcc/gcc.c:3379: warning: assignment from incompatible pointer type /d/home/des/tinderbox/src/contrib/gcc/gcc.c: In function `main': /d/home/des/tinderbox/src/contrib/gcc/gcc.c:5994: `FBSD_DATA_PREFIX' undeclared (first use in this function) /d/home/des/tinderbox/src/contrib/gcc/gcc.c:5994: (Each undeclared identifier is reported only once /d/home/des/tinderbox/src/contrib/gcc/gcc.c:5994: for each function it appears in.) *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu/usr.bin/cc/cc. *** Error code 1 Stop in /d/home/des/tinderbox/src/gnu/usr.bin/cc. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. *** Error code 1 Stop in /d/home/des/tinderbox/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
dump on current broken -- master/slave protocol botched
I have been using the following command to dump for months with no problem: dump 0fua /dev/nsa0 /dev/da0s1a for the past few weeks I get this: (bin)504}dump 0fua /dev/nsa0 /dev/da0s1a DUMP: Date of this level 0 dump: Wed Jun 5 19:54:04 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0s1a (/) to /dev/nsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 67590 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: master/slave protocol botched. DUMP: The ENTIRE dump is aborted. (bin)505} I restored dump from a tape from 5/3/2002 and it works fine : (bin)506}old.dump 0fua /dev/nsa0 /dev/da0s1a DUMP: Date of this level 0 dump: Wed Jun 5 19:56:05 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0s1a (/) to /dev/nsa0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 68395 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 68070 tape blocks on 1 volume DUMP: finished in 82 seconds, throughput 830 KBytes/sec DUMP: level 0 dump on Wed Jun 5 19:56:05 2002 DUMP: Closing /dev/nsa0 DUMP: DUMP IS DONE The hardware is SCSI adaptec controller: ahc0: Adaptec aic7880 Ultra SCSI adapter port 0xfc00-0xfcff mem 0xffbea000-0xffbeafff irq 10 at device 9.0 on pci0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs Disk: da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST19171W 0024 Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) Tape drive HP DDS2: sa0 at ahc0 bus 0 target 4 lun 0 sa0: HP C1533A A907 Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha boot1 UFS support: HELP NEEDED!
On Wed, 5 Jun 2002, Poul-Henning Kamp wrote: Somebody wh use sys/boot/common/ufsread.c before June 19th where the UFS2 patch is scheduled to be committed. This must not be needed, since old boot blocks must keep working with old file systems. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failure in libfetch
This seems not yet fixed even after libfetch commit. U lib/libfetch/Makefile U lib/libfetch/common.c U lib/libfetch/common.h U lib/libfetch/http.c U usr.bin/fetch/Makefile === usr.sbin/pkg_install/add cc -O -pipe -march=pentium -I/usr/src/usr.sbin/pkg_install/add/../lib -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/main.c cc -O -pipe -march=pentium -I/usr/src/usr.sbin/pkg_install/add/../lib -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/perform.c cc -O -pipe -march=pentium -I/usr/src/usr.sbin/pkg_install/add/../lib -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/futil.c cc -O -pipe -march=pentium -I/usr/src/usr.sbin/pkg_install/add/../lib -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/usr.sbin/pkg_install/add/extract.c cc -O -pipe -march=pentium -I/usr/src/usr.sbin/pkg_install/add/../lib -Wall -Wno-format-y2k -Wno-uninitialized -o pkg_add main.o perform.o futil.o extract.o /usr/obj/usr/src/usr.sbin/pkg_install/add/../lib/libinstall.a -lfetch -lmd /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_set_fd' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `X509_NAME_oneline' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_read' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_new' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_CTX_new' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_library_init' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `ERR_print_errors_fp' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_load_error_strings' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_CIPHER_get_name' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSLv23_client_method' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `X509_get_subject_name' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_get_current_cipher' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_connect' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `X509_get_issuer_name' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_get_peer_certificate' /usr/obj/usr/src/i386/usr/lib/libfetch.so: undefined reference to `SSL_write' *** Error code 1 Stop in /usr/src/usr.sbin/pkg_install/add. *** Error code 1 -- Jun Kuriyama [EMAIL PROTECTED] // IMG SRC, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make buildworld failure
Hi, make buildworld fails after the latest cvsup. The error I get is this - calvin# tail -30 /usr/ports/nooworld.log ranlib libcc_int.a === gnu/usr.bin/cc/cc cc -O -pipe -march=pentiumpro -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/usr/obj/usr/src/i386/usr\ -I/usr/obj/usr/src/i386/usr/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/config -DDEFAULT_TARGET_VERSION=\3.1\ -DDEFAULT_TARGET_MACHINE=\i386-undermydesk-freebsd\ -D__FBSDID=__RCSID -c /usr/src/contrib/gcc/gcc.c /usr/src/contrib/gcc/gcc.c: In function `process_command': /usr/src/contrib/gcc/gcc.c:3335: warning: passing arg 4 of `getobjformat' from incompatible pointer type /usr/src/contrib/gcc/gcc.c:3377: warning: assignment discards qualifiers from pointer target type /usr/src/contrib/gcc/gcc.c:3379: warning: assignment from incompatible pointer type /usr/src/contrib/gcc/gcc.c: In function `main': /usr/src/contrib/gcc/gcc.c:5994: `FBSD_DATA_PREFIX' undeclared (first use in this function) /usr/src/contrib/gcc/gcc.c:5994: (Each undeclared identifier is reported only once /usr/src/contrib/gcc/gcc.c:5994: for each function it appears in.) *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. calvin# exit exit Script done on Thu Jun 6 09:33:47 2002 calvin# uname -a FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Jun 3 17:54:43 IST 2002 root@calvin:/usr/obj/usr/src/sys/GENERIC i386 - Anything obviously wrong here ? TIA Regards Sid -- I've known him as a man, as an adolescent and as a child -- sometimes on the same day. Sid Carter FreeBSD oder Debian GNU/Linux. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failure in libfetch
On Thu, Jun 06, 2002 at 01:04:51PM +0900, Jun Kuriyama wrote: This seems not yet fixed even after libfetch commit. U lib/libfetch/Makefile U lib/libfetch/common.c U lib/libfetch/common.h U lib/libfetch/http.c U usr.bin/fetch/Makefile --- /usr/src/Makefile.inc1.orig Wed Jun 5 14:24:15 2002 +++ /usr/src/Makefile.inc1 Wed Jun 5 14:27:26 2002 @@ -720,6 +720,9 @@ _prebuild_libs+= secure/lib/libssh secure/lib/libssh__L: secure/lib/libcrypto__L lib/libz__L .endif +.if !defined(NO_OPENSSL) +_prebuild_libs+= secure/lib/libssl +.endif _generic_libs+=secure/lib .endif -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha boot1 UFS support: HELP NEEDED!
In message [EMAIL PROTECTED], Bruce Evans writes: On Wed, 5 Jun 2002, Poul-Henning Kamp wrote: Somebody wh use sys/boot/common/ufsread.c before June 19th where the UFS2 patch is scheduled to be committed. This must not be needed, since old boot blocks must keep working with old file systems. Does not compute. Old bootblocks are on the disks and nobody are changing them so they will keep working with what they work with. This change is necessary if the alpha architecture wants to be able to boot from a UFS2 filesystem in the future. The UFS2 patch btw allows the ufsread() function to be compiled in a UFS1 only or UFS1 or UFS2 configuration. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failure in libfetch
Michael Nottebrock [EMAIL PROTECTED] writes: make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libssl.a. Stop *expletive deleted* I didn't think of that. I'll commit a workaround ASAP, but I'm not sure how to fix it properly. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mergemaster broken?
In article [EMAIL PROTECTED], Bruce Evans [EMAIL PROTECTED] wrote: On Tue, 4 Jun 2002, walt wrote: It correctly identifies files to be updated, asks me what I want to do, as usual, and when I hit 'i' for install it proceeds without error messages but then it tells me at the end that all the files I told it to install remain for me to merge by hand. Read the messages more closely and you should see one about perl not being installed. The trouble is, those messages vanish in about 1 millisecond when the pager fires up and displays the next set of diffs. The messages are effectively invisible on my system, and I only found them by running mergemaster under script. Of course, Bruce, I have no doubt that you can see them on your Teletype Model 37. ;-) If mergemaster depends on perl and perl is not installed, it should be a fatal error which terminates mergemaster immediately. It doesn't make any sense to proceed if the merged files cannot be installed. John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: mergemaster broken?
The trouble is, those messages vanish in about 1 millisecond when the pager fires up and displays the next set of diffs. The messages are effectively invisible on my system, and I only found them by running mergemaster under script. Of course, Bruce, I have no doubt that you can see them on your Teletype Model 37. ;-) If you are using syscons terminal, you should be able to see previous output by pressing the scroll lock key, then page-up/page-down (and cursors keys). that's pretty usefull on a 80x24 terminal :) If mergemaster depends on perl and perl is not installed, it should be a fatal error which terminates mergemaster immediately. It doesn't make any sense to proceed if the merged files cannot be installed. In fact, IMHO, it doesn't make sense at all to have mergemaster depending on perl.. Since it's a system tools, it should use only sh/awk scripting.. my 2 cents.. fifi... John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa -- Guezou Philippe Net. Sys. Admin. Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld failure in libfetch
Ok, I finally feel the need to speak up here. DES, FREEFALL CVS IS NOT THE PLACE TO PUT EXPERIMENTAL CODE THAT BREAKS WORLD! PERIOD! Don't give me any crap about It's -current, you should expect breakage. You are abusing this disclaimer far more than it was ever meant for. Breaking world used to be a very humiliating event for committers. You, however, break it on a consistent basis. What the F*CK? Yes, others have broken world before you, and others will break it after you, but you are abusing the standards of the project. You know how to use branches in P4, and you know how to type cd /usr/src; make world What is so hard about doing this? Yes, it will slow down your ability to commit. Oh well. FreeBSD is about quality, and quality starts with code that builds. DES, you are hindering others who are trying to do work in -current. Most other committers make world before committing their stuff, and your disrespect to them is insulting and wastes time. Scott On Wed, Jun 05, 2002 at 11:22:54PM +0200, Dag-Erling Smorgrav wrote: Michael Nottebrock [EMAIL PROTECTED] writes: make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libssl.a. Stop *expletive deleted* I didn't think of that. I'll commit a workaround ASAP, but I'm not sure how to fix it properly. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] 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: buildworld failure in libfetch
On Wed, Jun 05, 2002 at 04:44:55PM -0600, Scott Long wrote: Ok, I finally feel the need to speak up here. I sent this patch to DES in private email, but it fixes world. Watch for cut-n-paste problems. troutmask:root[249] diff -u Makefile.inc1.orig Makefile.inc1 --- Makefile.inc1.orig Wed Jun 5 14:24:15 2002 +++ Makefile.inc1 Wed Jun 5 14:27:26 2002 @@ -720,6 +720,9 @@ _prebuild_libs+= secure/lib/libssh secure/lib/libssh__L: secure/lib/libcrypto__L lib/libz__L .endif +.if !defined(NO_OPENSSL) +_prebuild_libs+= secure/lib/libssl +.endif _generic_libs+=secure/lib .endif -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: alpha boot1 UFS support: HELP NEEDED!
On Wed, 5 Jun 2002, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Bruce Evans writes: On Wed, 5 Jun 2002, Poul-Henning Kamp wrote: Somebody wh use sys/boot/common/ufsread.c before June 19th where the UFS2 patch is scheduled to be committed. This must not be needed, since old boot blocks must keep working with old file systems. Does not compute. Old bootblocks are on the disks and nobody are changing them so they will keep working with what they work with. This change is necessary if the alpha architecture wants to be able to boot from a UFS2 filesystem in the future. This change is necessary in the future if someone wants to boot from a UFS2 file system. The UFS2 patch btw allows the ufsread() function to be compiled in a UFS1 only or UFS1 or UFS2 configuration. I'm surprised both fit in the i386 version. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump (via amanda) causing panics
On Wed, 5 Jun 2002, Brooks Davis wrote:
For the last week or so I've had my laptop panic every time amanda did
a dump of it. This happens with a kernel as of yesterday so it probably
wasn't just a bad update.
Before the crash I see the following in dmesg:
ad0: count 6359632 size transfers not supported
bus_dmamap_load: Too many segs! buf_len = 0xc204abb0
ad0: READ command tiemotu tag=0 serv=0 - resetting
ad0: resetting devices .. done
[the above repeated twice more]
ad0: count 6359632 size transfers not supported
bus_dmamap_load: Too many segs! buf_len = 0xc204abb0
ad0: READ command tiemotu tag=0 serv=0 - resetting
ad0: trying to fall back to PIO mode
ad0: resetting devices .. done
ad0: count 6359632 size transfers not supported
PANIC
This is caused by:
(1) amanda attempting to read from a bad offset on the device. Almost
any offset that causes a block number of = 2GB or 4GB will trigger
the kernel bug.
(2) the bounds checking in dscheck() being 64-bit daddr_t casualty
(*blush*).
I just committed this fix which I had been sitting on this fix for
too long:
%%%
Index: subr_diskslice.c
===
RCS file: /home/ncvs/src/sys/kern/subr_diskslice.c,v
retrieving revision 1.103
diff -u -2 -r1.103 subr_diskslice.c
--- subr_diskslice.c12 May 2002 20:49:41 - 1.103
+++ subr_diskslice.c23 May 2002 14:10:26 -
@@ -57,4 +57,5 @@
#include sys/malloc.h
#include sys/stat.h
+#include sys/stdint.h
#include sys/syslog.h
#include sys/vnode.h
@@ -225,5 +226,5 @@
/* beyond partition? */
- if (secno + nsec endsecno) {
+ if ((uintmax_t)secno + nsec endsecno) {
/* if exactly at end of disk, return an EOF */
if (secno == endsecno) {
@@ -232,10 +233,9 @@
}
/* or truncate if part of it fits */
- nsec = endsecno - secno;
- if (nsec = 0) {
+ if (secno endsecno) {
bp-bio_error = EINVAL;
goto bad;
}
- bp-bio_bcount = nsec * ssp-dss_secsize;
+ bp-bio_bcount = (endsecno - secno) * ssp-dss_secsize;
}
%%%
This fixes 2 overflow bugs. The main one is in the second hunk. Offsets
way beyond the end of the disk caused truncation to actually expand the
block to a huge one. (`nsec = endsecno - secno' subtracts a daddr_t that
is known to be positive from a u_long and stores the result in a long, so
overflow used to be only possible (for the assignment only) for physical
disks with more than 2GB sectors, but it is now possible for byte offsets
larger than 1TB which are much cheaper than 1TB disks.)
Device drivers that check the bounds directly probably have variants of this
bug. Ones that use the deprecated bounds_check_with_label() (mainly ccd and
drivers for ancient cdroms) certainly do.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
fixes for gcc -falign-foo
I have been using the following fixes for gcc -falign-foo for almost
a month with no problem.
%%%
Index: toplev.c
===
RCS file: /home/ncvs/src/contrib/gcc/toplev.c,v
retrieving revision 1.13
diff -u -2 -r1.13 toplev.c
--- toplev.c9 May 2002 22:15:04 - 1.13
+++ toplev.c12 May 2002 14:22:43 -
@@ -4747,5 +4747,5 @@
}
- if (optimize 2 || optimize_size)
+ if (optimize_size)
{
align_loops = 1;
Index: config/i386/i386.h
===
RCS file: /home/ncvs/src/contrib/gcc/config/i386/i386.h,v
retrieving revision 1.9
diff -u -2 -r1.9 i386.h
--- config/i386/i386.h 30 May 2002 06:04:14 - 1.9
+++ config/i386/i386.h 1 Jun 2002 20:49:25 -
@@ -762,5 +778,5 @@
/* Allocation boundary for the code of a function. */
-#define FUNCTION_BOUNDARY 16
+#define FUNCTION_BOUNDARY 8
/* Alignment of field after `int : 0' in a structure. */
%%%
The patch to toplev.c fixes a plain bug. gcc -O0 and -O1 didn't do
the easy optimization of alignment for space. They attempted to do
the easy optimization of alignment for time, which should be to 1-byte
alignment on i386's. However, the second bug forces the alignment to
2 bytes for functions only. The alignment should be to the
target-dependent default. This is in struct processor_target_table[]
in config/i386/i386.c on i386's. The defaults are very target-dependent
and much larger than 1 or 2 (e.g., 64 for align-jumps on athlons!).
The patch in i386.h permits -falign-foo=1 to work. It is not quite
right, because a boundary of 2 bytes is apparently required for C++.
This shouldn't be a problem, since the boundary shouldn't be 1 unless
the user really wants that boundary and sets it using -falign-functions=1.
However, the following cases give the too-small boundary of 1 even when
-falign-functions is not used:
- without the first patch: both -Oo and -O1
- with the first patch: -Os only.
The thread about the PR (http://gcc.gnu.org/ml/gcc/2002-05/msg00989.html)
doesn't seem to lead anywhere.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: fixes for gcc -falign-foo
Hey Bruce or David... has GCC3 by any chance fixed the stack alignment eyesore or is that still the default? If so could we by any chance fix it in our version? It creates massive bloat when you have lots of tiny functions and as far as I can tell there is no advantage at all except for the occassional floating point intensive app. I really hate having to specify -mpreferred-stack-boundary=2 in my builds. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: dump (via amanda) causing panics
On Thu, Jun 06, 2002 at 10:37:12AM +1000, Bruce Evans wrote: On Wed, 5 Jun 2002, Brooks Davis wrote: For the last week or so I've had my laptop panic every time amanda did a dump of it. This happens with a kernel as of yesterday so it probably wasn't just a bad update. This is caused by: (1) amanda attempting to read from a bad offset on the device. Almost any offset that causes a block number of = 2GB or 4GB will trigger the kernel bug. (2) the bounds checking in dscheck() being 64-bit daddr_t casualty (*blush*). This fixes the panic. It appears there's also another bug in dump though. When I run dump I get this: [10:15pm] brooks@minya (~): sudo dump -a -f /dev/null /var Password: DUMP: Date of this level 0 dump: Wed Jun 5 22:16:09 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/ad0s2e (/var) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 580085 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: master/slave protocol botched. DUMP: The ENTIRE dump is aborted. Any idea what this problem is? -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg39238/pgp0.pgp Description: PGP signature
Re: fixes for gcc -falign-foo
On Wed, 5 Jun 2002, Matthew Dillon wrote:
Hey Bruce or David... has GCC3 by any chance fixed the stack alignment
eyesore or is that still the default? If so could we by any chance fix
it in our version? It creates massive bloat when you have lots of tiny
functions and as far as I can tell there is no advantage at all except
for the occassional floating point intensive app. I really hate having
to specify -mpreferred-stack-boundary=2 in my builds.
Apparently not. It seems to have even added an extra stack alignment
instruction:
%%%
$ cat z.c
main()
{
foo();
bar(1, 2);
}
$ cc -O -S z.c
$ cat z.s
.file z.c
.text
.p2align 2,,3
.globl main
.type main,@function
main:
pushl %ebp
movl%esp, %ebp
subl$8, %esp
andl$-16, %esp ---
callfoo
subl$8, %esp
pushl $2
pushl $1
callbar
leave
ret
.Lfe1:
.size main,.Lfe1-main
.ident GCC: (GNU) 3.1 [FreeBSD] 20020509 (prerelease)
%%%
This andl is precisely what is needed to get the stack to a known alignment
starting from an unknown one, but I think it should only be done if the
function has any local variables that need more than 4-byte alignment
(and/or if the cpu arch cares). But in the above it is just an extra
instruction if the caller has already aligned the stack.
The alignment and the extra alignment is even down when it is obviously
just wasted:
%%%
$ cat z.c
main()
{
}
$ cc -O3 -S z.c
$ cat z.s
.file z.c
.text
.p2align 2,,3
.globl main
.type main,@function
main:
pushl %ebp
movl%esp, %ebp
subl$8, %esp-- old alignment
andl$-16, %esp -- new alignment
leave -- alignment not actually used
ret
.Lfe1:
.size main,.Lfe1-main
.ident GCC: (GNU) 3.1 [FreeBSD] 20020509 (prerelease)
%%%
I use the default for this except for compiling gcc itself.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: dump (via amanda) causing panics
On Wed, 5 Jun 2002, Brooks Davis wrote: This fixes the panic. It appears there's also another bug in dump though. When I run dump I get this: [10:15pm] brooks@minya (~): sudo dump -a -f /dev/null /var Password: DUMP: Date of this level 0 dump: Wed Jun 5 22:16:09 2002 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/ad0s2e (/var) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 580085 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: master/slave protocol botched. DUMP: The ENTIRE dump is aborted. Any idea what this problem is? I guess this is another 64-bit daddr_t problem. At least `daddr_t idblk[MAXNINDIR]' in traverse.c seems to be broken. This seems to be fixed in the ufs2 patch. There as another report about this earlier today, in a PR IIRC. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Removing perl usage from mergemaster
Hello dougb all,
Here's a patch that removes all trails of Perl usage from mergemaster.
The parts that I want your careful scrutiny directed at are the new
stat_mode() shell function, and the parts that I have touched lines
removing Perl code. I have done some testing to the resulting
mergemaster script, mostly by comparing the results of stat_mode() and
the old Perl code (having them both run, and print their output,
before mergemaster calls exit 1). If you find that you like the
changes, then the recent mergemaster problems on CURRENT machines that
have no perl port installed will go away ;)
I have tried to keep the code of stat_mode() clean, despite the fact
that it could possibly be written also as:
#
# Print in STDOUT the octal mode of a file and/or directory.
#
stat_mode () {
echo $(( ~$(echo obase=10; ibase=8; ${2} | bc )
$( echo obase=10;ibase=8;0 | bc )
$( echo obase=10; ibase=2; \
$( ls -ld ${1} | \
cut -c2-10 | \
sed -e '/^..[sS]/ s/^.*$/+1000/' \
-e '/^.[sS]/ s/^.*$/+100/' \
-e '/^[tT]/ s/^.*$/+10/' | \
sed -e 's/[st]/x/g' -e 's/ST/-/g' | \
sed -e 's/[rwx]/1/g' | \
sed -e 's/[^1+]/0/g' ) \
| bc )
)) | awk '{printf %04o\n, $0}'
}
The ls output parsing was inspired by an old post by Alfred Perlstein,
and I have only added the proper sed-lines to convert it to a valid
binary number. The rest, shell evaluations, substitutions and all is
something you can safely blame me for. Until now, I have verified
that this produces the same output, but it's admittedly harder to
decipher than the one I have included in the diff below. It is still
here, for us to use, if you all feel that it's better to avoid the use
of variables in stat_mode(). Whatever you all feel better with...
I think Doug's opinion as the maintainer of mergemaster is of the
utmost importance here. Anyone else with a better idea for removing
the dependency of mergemaster on Perl, is welcome to step up and offer
us his assistance though :)
Giorgos.
--- patch begins ---
Index: mergemaster.sh
===
RCS file: /home/ncvs/src/usr.sbin/mergemaster/mergemaster.sh,v
retrieving revision 1.31
diff -u -r1.31 mergemaster.sh
--- mergemaster.sh 28 May 2002 07:25:44 - 1.31
+++ mergemaster.sh 5 Jun 2002 21:25:09 -
@@ -214,6 +214,28 @@
esac
}
+stat_mode () {
+ pathname=$1
+ confirmed_umask=$2
+
+ decimal_umask=$( echo obase=10; ibase=8; ${confirmed_umask} | bc )
+ binary_mode=$( ls -ld ${pathname} | \
+ cut -c2-10 | \
+ sed -e '/^..[sS]/ s/^.*$/+1000/' \
+ -e '/^.[sS]/ s/^.*$/+100/' \
+ -e '/^[tT]/ s/^.*$/+10/' | \
+ sed -e 's/[st]/x/g' -e 's/ST/-/g' | \
+ sed -e 's/[rwx]/1/g' | \
+ sed -e 's/[^1+]/0/g' )
+ decimal_mode=$( echo obase=10; ibase=2; ${binary_mode} | bc )
+ mode_mask=$( echo obase=10;ibase=8;0 | bc )
+ masked_mode=$(( ${mode_mask} ${decimal_mode} ))
+ umasked_mode=$(( ${masked_mode} ~${decimal_umask} ))
+ octal_mode=$( echo ${umasked_mode} | awk '{printf %04o\n, $0}' )
+ unset decimal_umask binary_mode decimal_mode mode_mask masked_mode umasked_mode
+ echo ${octal_mode}
+}
+
# Set the default path for the temporary root environment
#
TEMPROOT='/var/tmp/temproot'
@@ -641,13 +663,11 @@
esac
if [ -n ${DESTDIR}${INSTALL_DIR} -a ! -d ${DESTDIR}${INSTALL_DIR} ]; then
-DIR_MODE=`perl -e 'printf %04o\n, (((stat($ARGV[0]))[2] 0) ~ \
- oct($ARGV[1]))' ${TEMPROOT}/${INSTALL_DIR} ${CONFIRMED_UMASK}`
+DIR_MODE=`stat_mode ${TEMPROOT}/${INSTALL_DIR} ${CONFIRMED_UMASK}`
install -d -o root -g wheel -m ${DIR_MODE} ${DESTDIR}${INSTALL_DIR}
fi
- FILE_MODE=`perl -e 'printf %04o\n, (((stat($ARGV[0]))[2] 0) ~ \
- oct($ARGV[1]))' ${1} ${CONFIRMED_UMASK}`
+ FILE_MODE=`stat_mode ${1} ${CONFIRMED_UMASK}`
if [ ! -x ${1} ]; then
case ${1#.} in
--- patch ends ---
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
