EGCS bootstrapping believed to be working
Hi all, I just committed a fix to the libstdc++ errors people see on the initial bootstrap from gcc 2.7.2 to EGCS. AFAIK, there are *NO* remaining bootstrap problems. If anybody has *ANY* bootstraping problems going from a pre-April 1st -CURRENT to the latest and greatest I want to hear about it. (only applies to the i386 platform) -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
On Wed, Apr 07, 1999 at 12:51:50AM -0700, David O'Brien wrote: AFAIK, there are *NO* remaining bootstrap problems. NOTE, I am assuming one is *NOT* using the -j option. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
* From: David O'Brien obr...@nuxi.com * * Hi all, * * I just committed a fix to the libstdc++ errors people see on the initial * bootstrap from gcc 2.7.2 to EGCS. AFAIK, there are *NO* remaining * bootstrap problems. I don't know about the bootstrapping problems but 4.0-snaps started showing up again on current.freebsd.org today (19990406) so I rebuilt the XFree86 (private) package and just started a whole-tree package build. Errors are starting to appear in http://bento.freebsd.org/~asami/errorlogs/4-latest/ -PW To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
I don't know about the bootstrapping problems but 4.0-snaps started showing up again on current.freebsd.org today (19990406) I wouldn't trust that 4.0-snap. That one should have a broken /usr/lib/libstdc++. I can send you working versions if you need. The 19990407 4.0-snap should be gold (well silver as we are still using the worse of the excptions stack unwinding method, jdp and I will change this soon) -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: I'll be in the Reading/London area this weekend...
Brian Somers writes: I'll be in the Reading / London area from Friday morning until Sunday evening. If there are any FreeBSD events taking place send me email and I'll try to pop around... There's one this evening (Wednesday) in London, but nothing on the weekend. If you're interested in a beer on Sunday afternoon, I'm sure I could persuade the family to let me out ;-) Perhaps a stopover here in Amsterdam might be on the order? :) Adrian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
* Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990403 17:33]: Existing MD5 passwords will still work. New users will get DES passwords. Thanks, but how do I get all my old users to use DES crypted passwords? Maybe I just should purify my network to loose those DES boxes and run FreeBSD md5 native only, that would be more secure and faster right? Not necessary at all to use the crypt and secure dirs in /usr/src right? If you dont need DES crypt that is, or is there any other advantage? I hope not, because then I will be happy and do no more cvsup to cvsup.internat.freebsd.org :-) Cheers! Anders -- Anders Andersson and...@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ Västgötagatan 11 Tel: +46-(0)31-168730 411 39 Gothenburg, SWEDEN Fax: +46-(0)31-209361 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New SiS 5591 ide chipset support.
The first thing is that I guess the no_dam should be no_dma, My understanding is that it stands for no damage. OK - I just thought it might have been a typo. Backing out the last change to ide_pci.c seems to fix the problem. I've lots of flags turned on in the kernel config file (0xa0ffa0ff), the old kernel complains a little but works fine, the new kernel spots that it is a SiS 5591, but grinds to a halt. Interesting. What motherboard do you have? Does it also have a 5595 on board? Its quite a cheap and nasty thing, but it works. I'll have a look when I get home and check. One way or another it's a problem with the new chipset support if it makes a previously working system no longer work. ide_pci0: SiS 5591 Bus-master IDE Controller rev 0xd0 int a irq 14 on pci0.0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 chip2: PCI to PCI bridge (vendor=1039 device=0001) rev 0x00 on pci0.2.0 Do you have the other chip reports as well? I'll have to check again when I get home. OK. Can I assume that you have only one drive on the machine? Have you tried a smaller DMA transfer size (say, to start with, 0xa001a001)? I actually have three drives and a cdrom on the two IDE busses, but it only seems to complain about the first one - I don't know if that is because it is the first one it tries to access or becauser the others work OK. I didn't take down the details of the other drives 'cos it takes ages to copy the stuff down. I did notice that it programed wd1 with transfer mode 22. Maybe I should try to take wd0 out of fstab and see if it works OK with wd1. I'll try it with a lower DMA transfer size too. David. David. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
Anders Andersson writes: * Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990403 17:33]: Existing MD5 passwords will still work. New users will get DES passwords. Thanks, but how do I get all my old users to use DES crypted passwords? Well, the short answer is 'you get them to change their password' . Which is true - you can't take an MD5 hash and turn it into a DES crypt, you'll need their cleartext password first. There are ways of achieving this in a large extent without their knowledge - firstly run crack, see what cleartext passwords you get. That is the easiest. My favourite though is to modify a daemon that uses cleartext authentication (say login, or the pop3 server you're using) to log sucessful attempts to a file which you can then troll for people's cleartext passwords, convert them to DES, and then only ask the few people left for a new password. Maybe I just should purify my network to loose those DES boxes and run FreeBSD md5 native only, that would be more secure and faster right? It depends entirely on the setup. I run DES purely because I have solaris and Digital UNIX boxen running DES. Not necessary at all to use the crypt and secure dirs in /usr/src right? If you dont need DES crypt that is, or is there any other advantage? I hope not, because then I will be happy and do no more cvsup to cvsup.internat.freebsd.org :-) If you need DES then you'll have to get the sources from a non-US site. Adrian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
Anders Andersson wrote: * Dag-Erling Smorgrav (d...@flood.ping.uio.no) [990403 17:33]: Existing MD5 passwords will still work. New users will get DES passwords. Thanks, but how do I get all my old users to use DES crypted passwords? Unfortunately, passwd(1) will helpfully maintain the same encryption method as was used before. ie: if a user has a MD5 passwd, the new one will also be MD5, regardless of the default. What I've wanted to do for some time is have a passwd re-coder launched from things like login etc when the plaintext password is available. I have wanted to be able to enable a transition to a new method over time. Of course, passwd(1) should ideally be able to be told to ignore the old method too - it looks like /etc/auth.conf is in the beginnings of this. (note that I'm not advocating changing the present system, just having the ability to do the two things above). Cheers, -Peter -- Peter Wemm pe...@netplex.com.au Netplex Consulting No coffee, No workee! :-) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
Anders Andersson and...@sanyusan.se writes: Maybe I just should purify my network to loose those DES boxes and run FreeBSD md5 native only, that would be more secure and faster right? More secure and *slower*. When it comes to password hashing, slower is better, because it makes brute force and dictionary attacks more expensive. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
* Peter Wemm (pe...@netplex.com.au) [990407 11:07]: Unfortunately, passwd(1) will helpfully maintain the same encryption method as was used before. ie: if a user has a MD5 passwd, the new one will also be MD5, regardless of the default. What I've wanted to do for some time is have a passwd re-coder launched from things like login etc when the plaintext password is available. I have wanted to be able to enable a transition to a new method over time. Of course, passwd(1) should ideally be able to be told to ignore the old method too - it looks like /etc/auth.conf is in the beginnings of this. (note that I'm not advocating changing the present system, just having the ability to do the two things above). Cheers, -Peter That sounds great Peter! Please let me know if you want me to test it for you. Anders -- Anders Andersson and...@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ Västgötagatan 11 Tel: +46-(0)31-168730 411 39 Gothenburg, SWEDEN Fax: +46-(0)31-209361 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New SiS 5591 ide chipset support.
OK. Can I assume that you have only one drive on the machine? Have you tried a smaller DMA transfer size (say, to start with, 0xa001a001)? I actually have three drives and a cdrom on the two IDE busses, but it only seems to complain about the first one - I don't know if that is because it is the first one it tries to access or becauser the others work OK. I didn't take down the details of the other drives 'cos it takes ages to copy the stuff down. I did notice that it programed wd1 with transfer mode 22. Maybe I should try to take wd0 out of fstab and see if it works OK with wd1. I'll try it with a lower DMA transfer size too. Erhm, the DMA transfer size has nothing to do with the multisector support that the 0x00ff00ff flags configures, it is all setup in ide_pci.c. It works by setting up a table of memory areas and lengths that should be transferred, and then the DMA hw does that all by magic ... If you want to mess with the transfer sizes thats where you could change it, but take my advise DONT!, that is not the cause of your problem. Did it work with generic DMA before, or did it just do PIO ?? If it worked, its the SIS support code thats at fault. -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New SiS 5591 ide chipset support.
On Wednesday, 7 April 1999 at 11:44:23 +0200, Soren Schmidt wrote: OK. Can I assume that you have only one drive on the machine? Have you tried a smaller DMA transfer size (say, to start with, 0xa001a001)? I actually have three drives and a cdrom on the two IDE busses, but it only seems to complain about the first one - I don't know if that is because it is the first one it tries to access or becauser the others work OK. I didn't take down the details of the other drives 'cos it takes ages to copy the stuff down. I did notice that it programed wd1 with transfer mode 22. Maybe I should try to take wd0 out of fstab and see if it works OK with wd1. I'll try it with a lower DMA transfer size too. Erhm, the DMA transfer size has nothing to do with the multisector support that the 0x00ff00ff flags configures, it is all setup in ide_pci.c. It works by setting up a table of memory areas and lengths that should be transferred, and then the DMA hw does that all by magic ... If you want to mess with the transfer sizes thats where you could change it, but take my advise DONT!, that is not the cause of your problem. Oops. Did it work with generic DMA before, or did it just do PIO ?? If it worked, its the SIS support code thats at fault. It's beginning to look like the latter. David's going to look at his system and find out what his chipset is. It looks like a relatively early version (it's older than my 18-month-old chipset), so maybe we'll have to do something based on revision level. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: aio_read
If it's a redirected output file you simply make it O_APPEND, at which point the seek offset in the descriptor becomes irrelevant. As others have pointed out, O_APPEND is much newer than the offset-sharing behavior. It also doesn't fix things for inputs. Of course with buffering, it's hard for it to have sensible semantics, but for some commands, it does work and can even useful. While I doubt many scripts rely on such behavior, it does avoid inconsistencies between internal and external commands, as well as files, ttys and pipes. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
* From: David O'Brien obr...@nuxi.com * I wouldn't trust that 4.0-snap. That one should have a broken * /usr/lib/libstdc++. I can send you working versions if you need. * * The 19990407 4.0-snap should be gold (well silver as we are still using * the worse of the excptions stack unwinding method, jdp and I will change * this soon) Thanks for the notice, but don't worry too much. I just meant to say I've restarted the regular package building on both 3.1 and 4.0 trees. By the way, do I need to rebuild the private XFree86 package when I grab a better snap or is that not necessary? (That part is not automatic) -PW To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
By the way, do I need to rebuild the private XFree86 package when I grab a better snap or is that not necessary? (That part is not automatic) I don't believe there are any C++ programs in XFree86, so you would be Ok. You would have noticed that C++ programs would not link. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Patched RealTek driver -- please test
This version survived for a little longer, but hung (on the 486 box) whilst doing a recursive ls of a large directory tree. Again, no messages, except for one which came up as the box was booting, whilst it was starting squid. The box was OK for about 4 minutes after this message, which was rl0: watchdog timeout Hope this helps. Stephen To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
* From: David O'Brien obr...@nuxi.com * I don't believe there are any C++ programs in XFree86, so you would be * Ok. You would have noticed that C++ programs would not link. Ok, thanks. BTW, the list of ports that built in 3.1 but failed in 4.0 are in http://bento.freebsd.org/~asami/errorlogs/4-latest-3-latest.html The netscape's are a known problem (no a.out libs), I don't know about the rest. -PW To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
make world error with ctm src-cur.3819
Hello, I just wanted to make egcs as the default compiler and tried to make world wit ctm src-cur.3819. I got the error message. Can anyone help ? Thanks. Clarence === Error === In file included from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/config/i386/xm-i386.h:43, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/hconfig.h:2, from /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/gengenrtl.c:22: /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: linux.h: No such file or directory /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:4: i386/freebsd-elf.h: No such file or directory *** Error code 1 Stop. === Error === To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
something's wrong with the in the last 24 hours with the sources
doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop === Tomer Weller s...@i.am well...@netvision.net.il Drugs are good, and if you do'em pepole think that you're cool, NoFX To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
/sys/boot, egcs vs. gcc, -Os
Now /sys/boot can't be compiled with gcc due to non-existent -Os added. Is it intentional or can be removed for backward compatibility? -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: something's wrong with the in the last 24 hours with the sources
Tomer Weller wrote: doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop Same here... I got the error and decided it was be being out of date on all the egcs stuff going around (I've been away recently)... I just did a straight 'buildworld' -Kp To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: something's wrong with the in the last 24 hours with the sources
I had this same problem last night after a fresh cvsup. I redid the make world without my normal -j4 and it completed fine. - Jason Tatem What you want is irrelevant. VC3, Inc. What you have chosen is at hand! tat...@vc3.com --Spock, Star Trek VI - On Wed, 7 Apr 1999, Tomer Weller wrote: doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop === Tomer Weller s...@i.am well...@netvision.net.il Drugs are good, and if you do'em pepole think that you're cool, NoFX To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: something's wrong with the in the last 24 hours with the sources
As it was pointed earlier in this list currently make world fails when -jn option is used. Try to compile without -jn. Jason Tatem wrote: I had this same problem last night after a fresh cvsup.? I redid the make world without my normal -j4 and it completed fine. - Jason Tatem What you want is irrelevant. VC3, Inc.?? What you have chosen is at hand! tat...@vc3.com? --Spock, Star Trek VI - On Wed, 7 Apr 1999, Tomer Weller wrote: doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop === ? Tomer Weller ? s...@i.am ? well...@netvision.net.il ? Drugs are good, and if you do'em ? pepole think that you're cool, NoFX To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Andrey A. Chernov wrote: Now /sys/boot can't be compiled with gcc due to non-existent -Os added. Is it intentional or can be removed for backward compatibility? It can be removed for backward compatibility. What it does is produce a smaller code. Egcs needs it, gcc doesn't. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org nothing better than the ability to perform cunning linguistics To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
current@
just wanted to point out i think this is a great mailing list, i just post a msg and get 4 replys in 30 minutes, keep up the good work guys/gals ! == Tomer Weller s...@i.am well...@netvision.net.il Drugs are good, and if you do'em pepole think that you're cool, NoFX To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
The 19990407 4.0-snap should be gold (well silver as we are still using the worse of the excptions stack unwinding method, jdp and I will change this soon) That snap and those following it are pending... Peter broke the compat lib stuff last night so the snaps are falling over again. :) - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: I'll be in the Reading/London area this weekend...
In message 19990407081419.28682.qm...@ewok.creative.net.au, adr...@freebsd.or G writes: Brian Somers writes: I'll be in the Reading / London area from Friday morning until Sunday evening. If there are any FreeBSD events taking place send me email and I'll try to pop around... There's one this evening (Wednesday) in London, but nothing on the weekend. If you're interested in a beer on Sunday afternoon, I'm sure I could persuade the family to let me out ;-) Perhaps a stopover here in Amsterdam might be on the order? Sorry, I'd have to bring a gun to make the flight do that... -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Some gcc/egcs comparisons
gcc compilation with -pipe -O2: 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse* 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 coolbrowse.static* 2064 -rwxr-xr-x 1 root wheel - 2104523 Mar 14 10:31 cooledit* 2992 -rwxr-xr-x 1 root wheel - 3054807 Mar 14 10:32 cooledit.static* 408 -rwxr-xr-x 1 root wheel - 405283 Mar 14 10:32 coolicon* 1360 -rwxr-xr-x 1 root wheel - 1378690 Mar 14 10:32 coolicon.static* 95 -rwxr-xr-x 1 root wheel - 96919 Mar 14 10:32 coolinput* 1064 -rwxr-xr-x 1 root wheel - 1075824 Mar 14 10:32 coolinput.static* 112 -rwxr-xr-x 1 root wheel - 104093 Mar 14 10:32 coollistbox* 1064 -rwxr-xr-x 1 root wheel - 1081051 Mar 14 10:32 coollistbox.static* 160 -rwxr-xr-x 1 root wheel - 148628 Mar 14 10:31 coolman* 1120 -rwxr-xr-x 1 root wheel - 1132445 Mar 14 10:32 coolman.static* 96 -rwxr-xr-x 1 root wheel - 97866 Mar 14 10:32 coolmessage* 1064 -rwxr-xr-x 1 root wheel - 1076561 Mar 14 10:32 coolmessage.static* 95 -rwxr-xr-x 1 root wheel - 96808 Mar 14 10:32 coolquery* 1064 -rwxr-xr-x 1 root wheel - 1075721 Mar 14 10:32 coolquery.static* egcs compilation with -pipe -Os: 112 -rwxr-xr-x 1 root wheel - 105524 Apr 7 18:58 coolbrowse* 880 -rwxr-xr-x 1 root wheel - 889540 Apr 7 18:58 coolbrowse.static* 1992 -rwxr-xr-x 1 root wheel - 2029127 Apr 7 18:57 cooledit* 2720 -rwxr-xr-x 1 root wheel - 2770319 Apr 7 18:57 cooledit.static* 416 -rwxr-xr-x 1 root wheel - 410957 Apr 7 18:58 coolicon* 1160 -rwxr-xr-x 1 root wheel - 1177536 Apr 7 18:58 coolicon.static* 112 -rwxr-xr-x 1 root wheel - 105020 Apr 7 18:58 coolinput* 880 -rwxr-xr-x 1 root wheel - 889228 Apr 7 18:58 coolinput.static* 120 -rwxr-xr-x 1 root wheel - 112610 Apr 7 18:58 coollistbox* 888 -rwxr-xr-x 1 root wheel - 894763 Apr 7 18:58 coollistbox.static* 176 -rwxr-xr-x 1 root wheel - 167248 Apr 7 18:57 coolman* 936 -rwxr-xr-x 1 root wheel - 948849 Apr 7 18:58 coolman.static* 112 -rwxr-xr-x 1 root wheel - 106107 Apr 7 18:58 coolmessage* 880 -rwxr-xr-x 1 root wheel - 889977 Apr 7 18:58 coolmessage.static* 112 -rwxr-xr-x 1 root wheel - 104861 Apr 7 18:58 coolquery* 880 -rwxr-xr-x 1 root wheel - 889073 Apr 7 18:58 coolquery.static* Seems like egcs really makes smaller binaries, except when the binary is small in itself already. Seems that after the size reaches roughly 10 bytes that egcs gets really active for optimisations. Featured program: CoolEdit 3.9.0 I unfortunately forgot to get the size of the static and shared libaries. Anyone got some details on that front? --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
On 07-Apr-99 Satoshi - the Wraith - Asami wrote: Errors are starting to appear in http://bento.freebsd.org/~asami/errorlogs/4-latest/ Weird that CoolEdit is on that list. I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work a-ok after patching up ltconfig to make shared libs. --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
EGCS
I can't get a make world to work with egcs. I deleted the whole obj directory, and recvsuppped the entire source tree, and it still doesn't work. Every time I cvsup I get a different error while compiling. Please Help. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: something's wrong with the in the last 24 hours with the sou
On 07-Apr-99 Karl Pielorz wrote: doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop Same here... I got the error and decided it was be being out of date on all the egcs stuff going around (I've been away recently)... I just did a straight 'buildworld' The problem lies with the function that -j tries to do: spawn multiple processes per cpu +1. This requires dependancy tuning in the Makefiles IIRC and wasn't be done yet in order to just focus on getting egcs to work. I believed Warner or someone else fixed that problem and its either commited or waiting for inclusion. In the meantime use no -j flags or try the -j[# of CPU + 1] thing. On a side note: profiled (-g) kernels with egcs work AFAICT. --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: EGCS
On 07-Apr-99 Kenneth Wayne Culver wrote: I can't get a make world to work with egcs. I deleted the whole obj directory, and recvsuppped the entire source tree, and it still doesn't work. Every time I cvsup I get a different error while compiling. OK, make sure ye go to /usr/src/gnu/usr.bin/cc first make clean, make obj, make depend, make, make install then try the libs in /usr/src/lib/ with roughly the same make targets. Then try to make a world again. HTH, --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Some gcc/egcs comparisons
In article xfmail.990407190505.asmo...@wxs.nl, Jeroen Ruigrok/Asmodai asmo...@wxs.nl wrote: gcc compilation with -pipe -O2: 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse* 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 coolbrowse.static* ... File sizes don't mean much. It would be more interesting to compare the outputs of size(1). John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Some gcc/egcs comparisons
On 07-Apr-99 John Polstra wrote: In article xfmail.990407190505.asmo...@wxs.nl, Jeroen Ruigrok/Asmodai asmo...@wxs.nl wrote: gcc compilation with -pipe -O2: 96 -rwxr-xr-x 1 root wheel - 97379 Mar 14 10:32 coolbrowse* 1064 -rwxr-xr-x 1 root wheel - 1076216 Mar 14 10:32 coolbrowse.static* ... File sizes don't mean much. It would be more interesting to compare the outputs of size(1). As thou wishes: gcc with -pipe -O2: [asmo...@daemon] (47) $ ll xfmail 760 -r-xr-xr-x 1 bin bin - 767720 Jan 1 16:08 xfmail* [asmo...@daemon] (49) $ size xfmail textdata bss dec hex filename 711165 53244 149924 914333 df39d xfmail [asmo...@daemon] (52) $ ll libxforms.so.0 512 -rw-r--r-- 1 root wheel - 513411 Jan 1 16:00 libxforms.so.0 [asmo...@daemon] (53) $ size libxforms.so.0 textdata bss dec hex filename 412781 29556 53092 495429 78f45 libxforms.so.0 Now for egcs with -pipe -Os: [asmo...@daemon] (30) # ll xfmail 808 -r-xr-xr-x 1 bin bin - 811812 Apr 7 19:39 xfmail* [asmo...@daemon] (31) # size xfmail textdata bss dec hex filename 753039 53616 150596 957251 e9b43 xfmail [asmo...@daemon] (16) # ll libxforms.so.0 512 -rw-r--r-- 1 root wheel - 513411 Apr 7 19:31 libxforms.so.0 [r...@daemon] (18) # size libxforms.so.0 textdata bss dec hex filename 412781 29556 53092 495429 78f45 libxforms.so.0 --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: something's wrong with the in the last 24 hours with the sources
On Wed, 7 Apr 1999, Tomer Weller wrote: doesn't matter how much i attempt to cvsup and make world in the last 24 hours i get this error, this is after i made world while interducing EGCS to FreeBSD, i had to do another make world cuz my C++ compiler couldn't make executables and that produces this situation. === cc_int make : dont know how to make insn-attrtab.c. Stop dont use make -j anything it is currently broken To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Installation changes?
Folks, I'm wondering if there have been some changes made in the installation procedure for -CURRENT from -STABLE? What I'm hoping for is a completely unattended installation procedure. Once I select what I want installed, I want to be able to select the installation method, input my configuration details for the machine, and then be able to walk away. I don't want to see any warnings about XFree-whatever being a required package but not (yet) installed, etc I certainly don't want to have to hit return a bazillion times to get through the warnings about XFree. If there is an ftp server timeout, I'd like to be able to have the program re-try with the same server after a specified amount of delay, specify a set of alternate servers to attempt to install with, or perhaps even have the program automatically test and determine which servers are responding most quickly. I'd also like to see an http installation method, one that would hopefully successfully make it through firewalls (and/or proxy servers), much better than either NFS or ftp. Thanks! I appreciate any information you can give me about upcoming changes to the installation procedure. -- Brad Knowles b...@shub-internet.org http://www.shub-internet.org/brad/ http://wwwkeys.pgp.net:11371/pks/lookup?op=getsearch=0xE38CCEF1 Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Thu, Apr 08, 1999 at 01:15:32AM +0900, Daniel C. Sobral wrote: Andrey A. Chernov wrote: Now /sys/boot can't be compiled with gcc due to non-existent -Os added. Is it intentional or can be removed for backward compatibility? It can be removed for backward compatibility. What it does is produce a smaller code. Egcs needs it, gcc doesn't. The problem is deeper. When I reemove it, I got this error: -2100 bytes available it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS optimizations
Alex Zepeda wrote: On Mon, 5 Apr 1999, Matthew Dillon wrote: There is nothing beyond -O2. Well, there's -O3, which tries to inline static functions, but that typically isn't beneficial because it really bloats up the code and subroutine calls on intel cpus are very fast. Really? The pgcc web page (goof.com/pcg) lead me to believe that there were a few more optimizations turned on by -O5 -O6.. - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message As far as I know, pgcc is different from egcs. I had pgcc, it did *significantly* better code than gcc at the time (about 1 to 2 years before), especially in floating point code, but it was buggy. I have egcs-1.2 (on a current-3.0) and I am rather disappointed with the code performance. With standard code without floating point calculations it does a bit worse than old gcc-2.7.x. In floating point (as in Mesa, ..) it is awful. It generates much slower code, than gcc-2.7.x. I am using an old Linpack benchmark (Calculate n linear equations) and I can get best perfomance usually with gcc-2.7.x using -O (*not* -O2!!). The same seems to be true with egcs, but more so. Egcs with x86-prozessors work best with -O, don't use more (-marchxxx does nothing significant). I understand there are reasons to switch to egcs (exceptions, C++ enhancements,..) but I hope they will do something for egcs' code performance. (Does code size really matter that much. Sure, it accumulates, but...). -- Helmut F. Wirth Email: hfwi...@teleweb.at To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Installation changes?
I'm wondering if there have been some changes made in the installation procedure for -CURRENT from -STABLE? Not enough to give you what you're asking for here, really. :( installed, etc I certainly don't want to have to hit return a bazillion times to get through the warnings about XFree. That, at least, is fixed however. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
fsck -p free() warnings on unconfigured drive
# fsck -p /dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7% fragmentation) /dev/rccd0c: CANNOT READ: BLK 16 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rccd0c: CANNOT SEEK: BLK -1 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rda0f: 12924 files, 157017 used, 26908 free (7796 frags, 2389 blocks, 4.2% fragmentation) /dev/rda0e: 2340 files, 21107 used, 58252 free (212 frags, 7255 blocks, 0.3% fragmentation) ccd0 was not configured the time I started fsck -- B.Walter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
In article 19990407221941.a91...@nagual.pp.ru, Andrey A. Chernov a...@nagual.pp.ru wrote: On Thu, Apr 08, 1999 at 01:15:32AM +0900, Daniel C. Sobral wrote: Andrey A. Chernov wrote: Now /sys/boot can't be compiled with gcc due to non-existent -Os added. Is it intentional or can be removed for backward compatibility? It can be removed for backward compatibility. What it does is produce a smaller code. Egcs needs it, gcc doesn't. The problem is deeper. When I reemove it, I got this error: -2100 bytes available it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. Why? The compiler in -current is egcs, not gcc. If you want to use the old compiler, then use the old sources for boot too. John -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: fsck -p free() warnings on unconfigured drive
Yep. It would be very good if you could capture a preferably small image of a filesystem which makes this happen and make it available to the committers via a PR Poul-Henning In message 19990407205026.a27...@cicely8.cicely.de, Bernd Walter writes: # fsck -p /dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7% fragmentation) /dev/rccd0c: CANNOT READ: BLK 16 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rccd0c: CANNOT SEEK: BLK -1 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rda0f: 12924 files, 157017 used, 26908 free (7796 frags, 2389 blocks, 4.2% fragmentation) /dev/rda0e: 2340 files, 21107 used, 58252 free (212 frags, 7255 blocks, 0.3% fragmentation) ccd0 was not configured the time I started fsck -- B.Walter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On 07-Apr-99 Andrey A. Chernov wrote: The problem is deeper. When I reemove it, I got this error: -2100 bytes available tried with -O2 yet? it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. This raises an interesting point I think. Do we need to maintain gcc/egcs compatibility? Or do we, since we track CURRENT, say: alas, that's progression for ye? Has there been an `official' consensus reached about this from core or commiters? --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: fsck -p free() warnings on unconfigured drive
On Wed, Apr 07, 1999 at 09:05:35PM +0200, Poul-Henning Kamp wrote: Yep. It would be very good if you could capture a preferably small image of a filesystem which makes this happen and make it available to the committers via a PR nothing to capure - because there ist no filesystem. I just needed to use fsck -p in single user mode without the need for any ccd volume so ccd0 was not configured. Poul-Henning In message 19990407205026.a27...@cicely8.cicely.de, Bernd Walter writes: # fsck -p /dev/rda0s1a: 2291 files, 34981 used, 4010 free (274 frags, 467 blocks, 0.7% fragmentation) /dev/rccd0c: CANNOT READ: BLK 16 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rccd0c: CANNOT SEEK: BLK -1 /dev/rccd0c: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: pointer to wrong page. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. fsck in free(): warning: page is already free. fsck in free(): warning: chunk is already free. /dev/rda0f: 12924 files, 157017 used, 26908 free (7796 frags, 2389 blocks, 4.2% fragmentation) /dev/rda0e: 2340 files, 21107 used, 58252 free (212 frags, 7255 blocks, 0.3% fragmentation) ccd0 was not configured the time I started fsck -- B.Walter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: fsck -p free() warnings on unconfigured drive
In message 19990407211508.a27...@cicely8.cicely.de, Bernd Walter writes: On Wed, Apr 07, 1999 at 09:05:35PM +0200, Poul-Henning Kamp wrote: Yep. It would be very good if you could capture a preferably small image of a filesystem which makes this happen and make it available to the committers via a PR nothing to capure - because there ist no filesystem. I just needed to use fsck -p in single user mode without the need for any ccd volume so ccd0 was not configured. Cool, even better then. Make a small shell script that does the needed stuff and send-pr the thing. GENERAL NOTE TO ALL USERS It is always the most important bit of information to include in a PR: detailed instructions on how to reproduce it. And I mean detailed! the best thing is a shell-script. /GENERAL NOTE TO ALL USERS Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: RE: EGCS optimizations
On Tue, 6 Apr 1999, David O'Brien wrote: Well what would be the chances of getting the pgcc patches committed? I'm quite interested in doing this, BUT only after the dust has settled on the EGCS import and the Alpha build is fixed. Also the 1.1.2 PGCC patches aren't available yet. jdp and I have another round of bootstraping to fix our current less-than-optimal exception handling. I want to wait a week or so until putting the changes into the tree. It's important to note that PGCC is NOWHERE NEAR production quality, last time I tried it, and not proven at all. I express no animosity toward PGCC itself, but unless it's been proven, I'd strongly oppose anything like this. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | http://www.freebsd.org _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Andrey A. Chernov wrote: The problem is deeper. When I reemove it, I got this error: -2100 bytes available it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. I didn't see any changes to loader/boot[012] lately. EGCS requires -Os, but gcc should be able to compile it within limits, just like in -stable. Are you sure you didn't test with egcs after removing -Os? -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org nothing better than the ability to perform cunning linguistics To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Thu, Apr 08, 1999 at 08:09:43AM +0900, Daniel C. Sobral wrote: -2100 bytes available it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. I didn't see any changes to loader/boot[012] lately. EGCS requires -Os, but gcc should be able to compile it within limits, just like in -stable. Are you sure you didn't test with egcs after removing -Os? Yes, of course I am shure. BTW, I see lots of malign options in cc call, maybe they play role. cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c /usr/src/sys/boot/i386/boot2/boot2.c -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Andrey A. Chernov wrote: On Thu, Apr 08, 1999 at 08:09:43AM +0900, Daniel C. Sobral wrote: -2100 bytes available it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. I didn't see any changes to loader/boot[012] lately. EGCS requires -Os, but gcc should be able to compile it within limits, just like in -stable. Are you sure you didn't test with egcs after removing -Os? Yes, of course I am shure. BTW, I see lots of malign options in cc call, maybe they play role. cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c /usr/src/sys/boot/i386/boot2/boot2.c Revision 1.12 of the Makefile contains option changes for egcs. If you want to use gcc, use rev 1.11 of the Makefile. (Jeez, guys!) -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
* Weird that CoolEdit is on that list. * * I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work * a-ok after patching up ltconfig to make shared libs. Did you click on the links to see what it's complaining about? It worked here doesn't mean much in this context, as the package building is done in a much more strict environment (empty /usr/local, PLIST checked (implicitly) by building package, etc.). -PW To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New SiS 5591 ide chipset support.
OK - I've made a little progress. It only seems to be the first drive that it doesn't like. I can boot the system fine with the new kernel as long as I don't go near wd0. I dunno if it likes wd2. I've included what seem to be the useful bits of a boot -v as seen by dmesg for both the new and the old kernel. I'm not sure if the old kernel was doing DMA - I think it was as it says it configured some drives for DMA, but it also says: generic_status: no PCI IDE timing info available I can't see far enough into the machine at the moment to see what is written on any of thi chips, but I guess that can be figured out from the PCI probes. The motherboard is an el cheapo P5SV-B Mainboard with what has to be one of the least professional pieces of documentation I've ever seen as a manual. David. Old kernel PCI probe: = Probing for devices on PCI bus 0: found- vendor=0x1039, dev=0x5571, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Host to PCI bridge (vendor=1039 device=5571) rev 0x01 on pci0.0.0 found- vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 found- vendor=0x1039, dev=0x5513, revid=0xc1 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 01f0, size 3 map[1]: type 4, range 32, base 03f4, size 2 map[2]: type 4, range 32, base 0170, size 3 map[3]: type 4, range 32, base 0374, size 2 map[4]: type 4, range 32, base 4000, size 4 ide_pci0: PCI IDE controller (busmaster capable) rev 0xc1 int a irq 14 on pci0.1.1 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 0 status: 64 from port: 4002 ide_pci: ide0:0 has been configured for DMA by BIOS ide_pci: ide0:1 has been configured for DMA by BIOS generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 1 status: 04 from port: 400a found- vendor=0x1039, dev=0x7001, revid=0xe0 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=9 found- vendor=0x1002, dev=0x4750, revid=0x5c class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 1, range 32, base e000, size 24 map[1]: type 4, range 32, base 6000, size 8 map[2]: type 1, range 32, base e100, size 12 vga0: ATI model 4750 graphics accelerator rev 0x5c on pci0.11.0 found- vendor=0x10cd, dev=0x1300, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 6100, size 8 map[1]: type 1, range 32, base e1001000, size 8 adv0: AdvanSys ASC3050 Ultra SCSI controller rev 0x03 int a irq 10 on pci0.13.0 adv0: AdvanSys Ultra SCSI Host Adapter, SCSI ID 7, queue depth 16 Old kernel wd probe === wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): ST32122A, DMA, 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc0: unit 1 (wd1): QUANTUM FIREBALL_TM2110A, DMA, 32-bit, multi-block-16 wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (wd2): Conner Peripherals 420MB - CFS420A, 32-bit, multi-block-64 wd2: 406MB (832608 sectors), 826 cyls, 16 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0003, dmamword = 0101, apio = , udma = wdc1: unit 1 (atapi): FX001DE/B05, removable, intr, iordis New kernel PCI probe Probing for devices on PCI bus 0: found- vendor=0x1039, dev=0x5571, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 chip0: Host to PCI bridge (vendor=1039 device=5571) rev 0x01 on pci0.0.0 found- vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 found- vendor=0x1039, dev=0x5513, revid=0xc1 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 01f0, size 3 map[1]: type 4, range 32, base 03f4, size 2 map[2]: type 4, range 32, base 0170, size 3 map[3]: type 4, range 32, base 0374, size 2 map[4]: type 4, range 32, base 4000, size 4 ide_pci0: SiS 5591 Bus-master IDE Controller rev 0xc1 int a irq 14 on pci0.1.1
Re: EGCS
On Wed, Apr 7, 1999, Kenneth Wayne Culver wrote: I can't get a make world to work with egcs. I deleted the whole obj directory, and recvsuppped the entire source tree, and it still doesn't work. Every time I cvsup I get a different error while compiling. CVSup now, and build world. Do _not_ attempt to build world with the -j flag, dependancies will fail to build properly and the compile will certainly fail. -Chris Please Help. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- = * This process can check if this value is * * zero, and if it is, it does something* * child-like. -Forbes Burkowski, CS 454 * = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
In article xfmail.990407210734.asmo...@wxs.nl, Jeroen Ruigrok/Asmodai asmo...@wxs.nl wrote: This raises an interesting point I think. Do we need to maintain gcc/egcs compatibility? Or do we, since we track CURRENT, say: alas, that's progression for ye? Yep, alas, that's progression for ye. We have never supported mix match of sourceballs from different releases. We do our best to support running old executables on newer systems, but that's a completely different issue. Has there been an `official' consensus reached about this from core or commiters? I am only speaking for John Polstra, a compiler guy, here. -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
In article 19990408040432.a74...@nagual.pp.ru, Andrey A. Chernov a...@nagual.pp.ru wrote: Yes, of course I am shure. BTW, I see lots of malign options in cc call, maybe they play role. cc -elf -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -fno-builtin -malign-functions=0 -malign-jumps=0 -malign-loops=0 -mrtd -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -c /usr/src/sys/boot/i386/boot2/boot2.c You removed the -Os but you didn't add back the -O2 that originally was there. -- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
* From: John Polstra j...@polstra.com * Yep, alas, that's progression for ye. We have never supported mix * match of sourceballs from different releases. We do our best * to support running old executables on newer systems, but that's a * completely different issue. : * I am only speaking for John Polstra, a compiler guy, here. Speaking for Satoshi Asami, the ports guy, I agree with John. I for one will hate to see the ports people having to worry about 4.0-gcc (they already have 4.0-egcs and 3.1-gcc to worry about...). -PW To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world error with ctm src-cur.3819
I just wanted to make egcs as the default compiler and tried to make world ... /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/egcs/gcc/tm.h:3: linux.h: No such file or directory The fact you are refering to linux.h says you've some kind of error... I never commited linux.h or refered to it in what I commited. IF you grabed my earily EGCS from my personal machine, then you could have this reference. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Wed, Apr 07, 1999 at 05:50:24PM -0700, John Polstra wrote: You removed the -Os but you didn't add back the -O2 that originally was there. Thanx, it works now. It was the reason I overlook. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC+ D A a++ C G+ QH+(++) 666+++ Y To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
Of course, passwd(1) should ideally be able to be told to ignore the old method too - it looks like /etc/auth.conf is in the beginnings of this. When I proposed changing this and adding a knob in auth.conf, it was said PAM is really the place for this. Actually a committed (forgot who) tried to overhall the crypt stuff a few months ago and it blew up in his face. I don't think anyone has changed since. A shame. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: EGCS
On Wed, 7 Apr 1999, Chris Costello wrote: On Wed, Apr 7, 1999, Kenneth Wayne Culver wrote: I can't get a make world to work with egcs. I deleted the whole obj directory, and recvsuppped the entire source tree, and it still doesn't work. Every time I cvsup I get a different error while compiling. CVSup now, and build world. Do _not_ attempt to build world with the -j flag, dependancies will fail to build properly and the compile will certainly fail. And note that there have been several little bugs that have been cleared already, so if it doesn't do it the first time, have faith and cvsup again. It's built twice bad for me (the first 2 times) and since, twice good. -Chris Please Help. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- = * This process can check if this value is * * zero, and if it is, it does something* * child-like. -Forbes Burkowski, CS 454 * = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Wed, 7 Apr 1999, John Polstra wrote: In article xfmail.990407210734.asmo...@wxs.nl, Jeroen Ruigrok/Asmodai asmo...@wxs.nl wrote: This raises an interesting point I think. Do we need to maintain gcc/egcs compatibility? Or do we, since we track CURRENT, say: alas, that's progression for ye? Yep, alas, that's progression for ye. We have never supported mix match of sourceballs from different releases. We do our best to support running old executables on newer systems, but that's a completely different issue. Has there been an `official' consensus reached about this from core or commiters? I am only speaking for John Polstra, a compiler guy, here. John, no complaint (I figure some recompiling is the cost of running current) but could you please repost here some stuff that I think you said once already? I'm sorry, but I have an error, and I want to make sure it's recompile time. Here's the last part of the dump: configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os -pipe -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/l ocal/include/giflib -s -L/usr/local/lib -L/usr/X11R6/lib conftest.C -lkdecore -lqt -lXext -lX11 -rpath /usr/local/lib -rpath /usr/X11R6/lib 15 /usr/libexec/elf/ld: warning: libstdc++.so.2, needed by /usr/local/lib/libkdecore.so, may conflict with libstdc++.so.3 /usr/lib/libstdc++.so.2: undefined reference to `__unwind_function' /usr/lib/libstdc++.so.2: undefined reference to `__find_first_exception_table_match' /usr/local/lib/libkdecore.so: undefined reference to `_vt$11QPushButton$12QPaint Device' /usr/lib/libstdc++.so.2: undefined reference to `__register_exceptions' /usr/local/lib/libkdecore.so: undefined reference to `_vt$11QPushButton' I thought you had patched ld-elf.so.1 so this (__register_exceptions) wouldn't get hit again, but maybe I'm wrong, could you please bang me on the head with the story, and THIS TIME I'll try to remember it? +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Chuck Robey wrote: configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os -pipe -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/l ocal/include/giflib -s -L/usr/local/lib -L/usr/X11R6/lib conftest.C -lkdecore -lqt -lXext -lX11 -rpath /usr/local/lib -rpath /usr/X11R6/lib 15 /usr/libexec/elf/ld: warning: libstdc++.so.2, needed by /usr/local/lib/libkdecore.so, may conflict with libstdc++.so.3 Bzzt. You've got something old that's still using libstdc++.so.2. You can't combine that with something that uses libstdc++.so.3. I.e., you can't use both versions at the same time. I'd suggest rebuilding the port and everything that it depends upon. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Wed, 7 Apr 1999, John Polstra wrote: Chuck Robey wrote: configure:4096: /bin/sh ./libtool --silent --mode=link c++ -o conftest -Os -pipe -I/usr/local/include -I/usr/X11R6/include/X11/qt -I/usr/X11R6/include -I/usr/l ocal/include/giflib -s -L/usr/local/lib -L/usr/X11R6/lib conftest.C -lkdecore -lqt -lXext -lX11 -rpath /usr/local/lib -rpath /usr/X11R6/lib 15 /usr/libexec/elf/ld: warning: libstdc++.so.2, needed by /usr/local/lib/libkdecore.so, may conflict with libstdc++.so.3 Bzzt. You've got something old that's still using libstdc++.so.2. You can't combine that with something that uses libstdc++.so.3. I.e., you can't use both versions at the same time. I'd suggest rebuilding the port and everything that it depends upon. Thanks for the clue, John! As much as I hate redoing the KDE and gnome ports, it looks like doing that again ... John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Chuck Robey wrote: Thanks for the clue, John! As much as I hate redoing the KDE and gnome ports, it looks like doing that again ... I don't blame you. I've never even built them, for the simple (lazy) reason that they looked like they'd be too painful to upgrade. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Wed, 7 Apr 1999, John Polstra wrote: Chuck Robey wrote: Thanks for the clue, John! As much as I hate redoing the KDE and gnome ports, it looks like doing that again ... I don't blame you. I've never even built them, for the simple (lazy) reason that they looked like they'd be too painful to upgrade. I'm very close to relying on packages for them. I'll have to see if there are *very* up-to-date packages. If there aren't, and I end up having to rebuild the mess, would you want to pack up some packages from me? They'll be strictly current-based, and I won't bother you until a collection is complete (if you have interest .. some are interesting). Understand I'll probably take at least 10 days to do this. John --- John Polstra j...@polstra.com John D. Polstra Co., Inc.Seattle, Washington USA Self-interest is the aphrodisiac of belief. -- James V. DeLong +--- Chuck Robey | Interests include any kind of voice or data chu...@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
* From: Chuck Robey chu...@mat.net * I'm very close to relying on packages for them. I'll have to see if * there are *very* up-to-date packages. If there aren't, and I end up As long as they build, FTP packages are usually within one week (usually less) of the ports tree on both 3.1 and 4.0. -PW To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
System hangs when booting with (update5) of ata/atapi driver
my system hangs when booting with update5 of the ata/atapi driver with the following in my kernel config: controller ata0 device atadisk0# ATA disks device atapifd0# ATAPI floppy drives the boot messages: Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=1039 device=5591) rev 0x02 on pci0.0.0 ata-pci0: Unknown PCI IDE Controller rev 0xd0 int a irq 14 on pci0.0.1 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq on ata-pci0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 chip2: PCI to PCI bridge (vendor=1039 device=0001) rev 0x00 on pci0.2.0 [snippage ...] ata0: master: setting up generic WDMA2 mode OK ad0: FUJITSU MPB3032ATU/2011 ATA-3 disk at ata0 as master ad0: 3039MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s1a and then the system hangs. pressing reset and booting /kernel.old brings it back to life. now with the following entries in my kernel config: controller wdc0at isa? port IO_WD1 bio irq 14 flags 0x80ff80ff disk wd0 at wdc0 drive 0 optionsATAPI#Enable ATAPI support for IDE bus optionsATAPI_STATIC #Don't do it as an LKM i get the following on boot and all is well ... Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=1039 device=5591) rev 0x02 on pci0.0.0 ide_pci0: SiS 5591 Bus-master IDE Controller rev 0xd0 int a irq 14 on pci0.0.1 chip1: SiS 85c503 rev 0x01 on pci0.1.0 chip2: PCI to PCI bridge (vendor=1039 device=0001) rev 0x00 on pci0.2.0 [snip ...] wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): FUJITSU MPB3032ATU, 32-bit, multi-block-16 wd0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S my motherboard is a gigabyte ga-5sg11 with SIS 5591/5595 chipset.. hope this info is helpful ... #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
it seems that boot2 needs to be reduced, and I don't know why it becomes that big and what can be reduced. First candidates are static cmd[512] and kernel[1024]. Please fix so it can be still compiled with gcc. Why? The compiler in -current is egcs, not gcc. If you want to use the old compiler, then use the old sources for boot too. Everything should be buildable with CC=aac (any ANSI compiler), but that's asking too much for programs like kernels and boot blocks. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Bruce Evans wrote: Everything should be buildable with CC=aac (any ANSI compiler), but that's asking too much for programs like kernels and boot blocks. The problem in this case is just that the compilers require different command line options. It's asking _way_ too much to require those to be identical. John To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Everything should be buildable with CC=aac (any ANSI compiler), but
that's asking too much for programs like kernels and boot blocks.
The problem in this case is just that the compilers require
different command line options. It's asking _way_ too much to
require those to be identical.
Actually, they don't. Compiler-specific options can be put in ${CC}.
Perhaps they even should be.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Bruce Evans wrote:
The problem in this case is just that the compilers require
different command line options. It's asking _way_ too much to
require those to be identical.
Actually, they don't. Compiler-specific options can be put in ${CC}.
Perhaps they even should be.
But in this case, we want -Os (egcs) or -O2 (gcc) only for
building boot -- not for everything. It could be parameterized with
make macros like OPT_SMALL and OPT_FAST in the *.mk files, I
suppose.
John
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
ftp hangs on -current
ftp on 4.0-very-current (post egcs make world) randomly hangs during sessions... I never succeded in finishing a session lately. To transfer some files from my home to my isp server I had to do an ftp from the server and a get to them... The ftp server works normally and fetch is ok ... Probably it is a fault of my system, if no other experiences it. Thanks for attention... Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Wed, 7 Apr 1999, Chuck Robey wrote: Bzzt. You've got something old that's still using libstdc++.so.2. You can't combine that with something that uses libstdc++.so.3. I.e., you can't use both versions at the same time. I'd suggest rebuilding the port and everything that it depends upon. Thanks for the clue, John! As much as I hate redoing the KDE and gnome ports, it looks like doing that again ... That was one of the BIG pitfalls of egcs, binary incompatable C++ programs and libs. Sounds like you're overdue for your favorite shot of caffiene. - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
On Wed, 7 Apr 1999, John Polstra wrote: Chuck Robey wrote: Thanks for the clue, John! As much as I hate redoing the KDE and gnome ports, it looks like doing that again ... I don't blame you. I've never even built them, for the simple (lazy) reason that they looked like they'd be too painful to upgrade. Bah, if the ports-tree can make building Gnome easy, it's hardly painful (and I know KDE is easy to build from tarballs). It just takes a bit of patience. - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /sys/boot, egcs vs. gcc, -Os
Actually, they don't. Compiler-specific options can be put in ${CC}.
Perhaps they even should be.
But in this case, we want -Os (egcs) or -O2 (gcc) only for
building boot -- not for everything. It could be parameterized with
make macros like OPT_SMALL and OPT_FAST in the *.mk files, I
suppose.
CC+=-Os in individual Makefiles works about as well as CFLAGS+=-Os for
adding flags. That's not very well. Removing unwanted additions is hard.
BTW, boot2/Makefile uses CFLAGS= to override any previous definition
of CFLAGS. This may break `make world' by removing -nostdinc.
Bruce
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: EGCS bootstrapping believed to be working
On 08-Apr-99 Satoshi - the Wraith - Asami wrote: * Weird that CoolEdit is on that list. * * I built both 3.8.3 and 3.9.0 by hand here using gcc and egcs, both work * a-ok after patching up ltconfig to make shared libs. Did you click on the links to see what it's complaining about? It worked here doesn't mean much in this context, as the package building is done in a much more strict environment (empty /usr/local, PLIST checked (implicitly) by building package, etc.). Sure it means much, I am the libtool nagging guy *g* This means that I always verify ltconfig. Now go look at the cooledit logs, someone forgot to patch ltconfig to create shared libraries. The patch is straightforward and I believe 3.9.0 has this incorporated and else maintainer oughtta be nagging the programmers about migrating to libtool 1.2f to at least solve the shared library problem on FreeBSD 4.x. Probably tons of others in that list... I will look at the log today and give ye an oversight of the ltconfig problemcases... --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org asmodai(at)wxs.nlThe idea does not replace the work... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
