Re: Internal compiler error: program ld got fatal signal 10

2000-05-30 Thread Hasan Diwan
Shouldn't the following command be part of the linux_base port along with: echo 'As of 2529, all Linux statically linked binaries must be explicitly branded ELF' I would add it myself, except my FreeBSD box is currently down. :( On Mon, May 29, 2000 at 10:11:29AM +0200, Jose M. Alcaide wrote:

Re: Internal compiler error: program ld got fatal signal 10

2000-05-29 Thread Jose M. Alcaide
"Mark C. Langston" wrote: > > On Sun, May 28, 2000 at 08:55:37PM -0600, Warner Losh wrote: > > The patch works for me! Yippie! I have my AJ back again. > > I don't know if this is related, but: > > I cvsup'd to -CURRENT this evening (my first attempt to do so), and am > now seeing the followi

Re: Internal compiler error: program ld got fatal signal 10

2000-05-29 Thread Mark C. Langston
On Sun, May 28, 2000 at 08:55:37PM -0600, Warner Losh wrote: > The patch works for me! Yippie! I have my AJ back again. I don't know if this is related, but: I cvsup'd to -CURRENT this evening (my first attempt to do so), and am now seeing the following error on boot: pid 156 (ldconfig), uid

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> "David O'Brien" writes: : On Sun, May 28, 2000 at 08:32:30PM -0600, Warner Losh wrote: : > If it works, then I think it should be committed in the usual way : > for this stuff: Filtered through David O'Brien... : : Give me a few days if you can. (if people th

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread David O'Brien
On Sun, May 28, 2000 at 08:32:30PM -0600, Warner Losh wrote: > If it works, then I think it should be committed in the usual way > for this stuff: Filtered through David O'Brien... Give me a few days if you can. (if people think that is unacceptable, please let me know) I've forwarded the

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread David O'Brien
On Mon, May 29, 2000 at 05:05:29AM +, Anatoly Vorobey wrote: > You need to apply the patch and remake /usr/src/gnu/usr.bin/binutils/libbfd > and then /usr/src/gnu/usr.bin/binutils/ld . I'll pass this onto the Binutils people. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
The patch works for me! Yippie! I have my AJ back again. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Steve Kargl
Warner Losh wrote: > David, > I'm fairly certain that there are malloc related bugs in the new > binutils. If I have malloc.conf pointing at AJ, then we die in ld all > the time. If I remove that file, then we don't and things appear to > work. That's why some people succeeded in their upgrade,

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Anatoly Vorobey writes: : Can you test this patch? I think I tracked down the problem. At some : point, someone added a new field into a hash table struct and didn't : add initialization for it into the general hash table struct init func. : This patch cures the prob

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Anatoly Vorobey
On Sun, May 28, 2000 at 05:12:05PM -0600, Warner Losh wrote: > I get these failures on hello world: > > int main() { printf("hello world\n"); } > > cc -c xxx.c > cc -o xxx xxx.o > Can you test this patch? I think I tracked down the problem. At some point, someone added a new field into a hash

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Anatoly Vorobey
On Sun, May 28, 2000 at 05:12:05PM -0600, Warner Losh wrote: > I think that this is strong evidence that there are bugs in the new > binutils that AJ is finding. I think it may be that it incorrectly > expects memory to be zero'd when it gets it or something. I've further verified that: - it's

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
David, looks like I found the problem. Or at least how to trivially recreate the problem and how to work around it for those people that need to do so. I've cc'd current since I've been talking there with people about it. I'm fairly certain that there are malloc related bugs in the new

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
Did install of new binutils. now ld dumps core ALL the time. Further testing impossible. DO NOT TRY TO UPGRADE JUST BINUTILS IF YOU ARE GETTING THE SIGNAL 10 ERROR. YOU WON'T BE ABLE TO BUILD ANYTHING ELSE ON THE SYSTEM. Now, I'm grumpy... Warner To Unsubscribe: send mail to [EMAI

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Warner Losh writes: : OK. I'm trying on my bouncer box now. It is over NFS so it is slow. : Also it is a PPro 180, so that is slow too :-(. : : FreeBSD billy-club.village.org 5.0-CURRENT FreeBSD 5.0-CURRENT #33: : Sun Apr 30 22:57:58 MDT 2000 : [EMAIL PROTECTED]:/

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : make world : reboot : rebuild+install kernel : reboot OK. I'm trying on my bouncer box now. It is over NFS so it is slow. Also it is a PPro 180, so that is slow too :-(. FreeBSD billy-club.village.org 5.0-CURRENT FreeBSD 5.0-CUR

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Thomas D. Dean
Sorry for two replies: I did: make world reboot rebuild+install kernel reboot tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Thomas D. Dean
Before upgrade: FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #0: \ Tue Apr 4 11:47:34 PDT 2000 \ [EMAIL PROTECTED]:/usr/src/sys/compile/CELEBRIS-SMP i386 After upgrade: FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #1: \ Sun May 28 11:07:09 PDT 2000 \ root@celebris:/usr/src/sy

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> John Baldwin writes: : I built a new world fine with the new binutils right after all my commits : in /sys/boot. Also, I built world again with today's sources: OK. I have the old binutils installed on my system. : -- : build

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread John Baldwin
On 28-May-00 Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: >: I just completed a 'make world' on a -current cvsup'ed yesterday and saw >: no errors. > > When was the previous time that you did this? And did you update the > binutils first? It sure would be a MAJO

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Szilveszter Adam
On Sun, May 28, 2000 at 01:10:20PM -0600, Warner Losh wrote: > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: > : I just completed a 'make world' on a -current cvsup'ed yesterday and saw > : no errors. > > When was the previous time that you did this? And did you update the > binutils f

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Steve Kargl writes: : I've got 500MB of swap. It is never touched during : the build. The machine is very lightly loaded (i.e., : only "make buildworld" running). Ditto. I just tried it with root and all the limits set to unlimited. I had the same problem. : I

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Steve Kargl
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: > : The ability to do cross builds rules out the need to update binutils > : first. I haven't done any cross-builds since, well, februari, so I'm not > : at all up to date on that front; things may have been broken by the

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: : The ability to do cross builds rules out the need to update binutils : first. I haven't done any cross-builds since, well, februari, so I'm not : at all up to date on that front; things may have been broken by then... I did a complete buil

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Marcel Moolenaar
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: > : I just completed a 'make world' on a -current cvsup'ed yesterday and saw > : no errors. > > When was the previous time that you did this? And did you update the > binutils first? It sure would be a MAJOR BUMMER

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Thomas D. Dean" writes: : I just completed a 'make world' on a -current cvsup'ed yesterday and saw : no errors. When was the previous time that you did this? And did you update the binutils first? It sure would be a MAJOR BUMMER if one needed to update binutils f

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Thomas D. Dean
I just completed a 'make world' on a -current cvsup'ed yesterday and saw no errors. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
Here's the full list. I think something very bad is going on here. Here's the list from my last build: i386/usr/lib/libc.so: file not recognized: File truncated i386/usr/lib/libcalendar.so: file not recognized: File truncated i386/usr/lib/libcrypt.so: file not recognized: File truncated i386/usr

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Martin Cracauer writes: : I know that it is supposed to do so, I suspect that might not be the : case here. I don't think so. It is already using the new ld when it coredumps. I don't think that having it on the system would change things much. BTW, if I do a make

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Steve Kargl
Warner Losh wrote: > In message <[EMAIL PROTECTED]> Bob Martin writes: > : If you are using an older K6 with more than 32mb of ram, this will > : happen from time to time of it's own accord. I have never taken the time > : to find out why, but if you search the archives, you will find that it > :

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Martin Cracauer
In <[EMAIL PROTECTED]>, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Martin Cracauer writes: > : Have you tried building and installing the new binutils before > : compiling the rest of the world? > > This shouldn't be required for buildworld. If it is, then it is a bug > in the buildwor

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Martin Cracauer writes: : Have you tried building and installing the new binutils before : compiling the rest of the world? This shouldn't be required for buildworld. If it is, then it is a bug in the buildworld process. Buildworld makes all the stuff it needs to

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Bob Martin writes: : If you are using an older K6 with more than 32mb of ram, this will : happen from time to time of it's own accord. I have never taken the time : to find out why, but if you search the archives, you will find that it : happens quite a bit. I'm usi

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Warner Losh
In message <[EMAIL PROTECTED]> Steve Kargl writes: : cc: Internal compiler error: program ld got fatal signal 10 : : *default date=2000.05.23.00.00.00 : : as specified in my cvsup supfile. The system builds fine : for all earlier dates that I've tried. I have used the : following t

Re: Internal compiler error: program ld got fatal signal 10

2000-05-28 Thread Martin Cracauer
t; cc: Internal compiler error: program ld got fatal signal 10 > *** Error code 1 > > Stop in /usr/src/lib/libmd. > *** Error code 1 > > > Now, the details. I started on Monday trying to update > a 15 March 00 -current to current -current. I get the > above error

Re: Internal compiler error: program ld got fatal signal 10

2000-05-27 Thread Steve Kargl
Bob Martin wrote: > > with "unsubscribe freebsd-current" in the body of the message > If you are using an older K6 with more than 32mb of ram, this will > happen from time to time of it's own accord. I have never taken the time > to find out why, but if you search the archives, you will find that

Re: Internal compiler error: program ld got fatal signal 10

2000-05-27 Thread Bob Martin
Steve Kargl wrote: > > First, the error message: > > cc -fpic -DPIC -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF >-I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libmd/i386/rmd160.S -o rmd160.So > building shared library libmd.so.2 > cc: Internal compiler

Internal compiler error: program ld got fatal signal 10

2000-05-27 Thread Steve Kargl
First, the error message: cc -fpic -DPIC -I/usr/src/lib/libmd -DSHA1_ASM -DELF -DRMD160_ASM -DELF -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libmd/i386/rmd160.S -o rmd160.So building shared library libmd.so.2 cc: Internal compiler error: program ld got fatal signal 10 *** Error code 1