Re: Internal compiler error: program ld got fatal signal 10
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: > brandelf -t Linux /compat/linux/sbin/ldconfig -- Hasan Diwan [[EMAIL PROTECTED]] Computer Science Department Rensselaer Polytechnic Institute PGP signature
Re: Internal compiler error: program ld got fatal signal 10
"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 following error on boot: > > pid 156 (ldconfig), uid 0: exited on signal 11 (core dumped) > > I applied the patch from earlier in the thread, followed the > instructions, and still no luck. Unfortunately, I'm not at all > familiar with using gdb to debug the resulting corefile, but if anyone > needs any information from it can cares to walk me through the steps > necessary to obtain it, I'll be glad to. > I think your problem is caused by linux_base's ldconfig, which now must be explicitly branded (and all static Linux binaries): brandelf -t Linux /compat/linux/sbin/ldconfig Hope this helps, -- JMA --- José Mª Alcaide | mailto:[EMAIL PROTECTED] Universidad del País Vasco | mailto:[EMAIL PROTECTED] Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 --- "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
Re: Internal compiler error: program ld got fatal signal 10
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 0: exited on signal 11 (core dumped) I applied the patch from earlier in the thread, followed the instructions, and still no luck. Unfortunately, I'm not at all familiar with using gdb to debug the resulting corefile, but if anyone needs any information from it can cares to walk me through the steps necessary to obtain it, I'll be glad to. -- Mark C. Langston [EMAIL PROTECTED] Systems & Network Admin San Jose, CA 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
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 think that is unacceptable, : please let me know) I've forwarded the patch to the Binutils : maintainers. Binutils 2.10 should be released any day now, so I'll have : to do another Buntils import anyway, so I'll get it then. I think a few days is cool. There's a known work around for the problem, and it doesn't seem to cause any problems. People that are really worried can apply the patch. Yes, it is a breakage, and it was frustrating to find out what broke, but now that we know the parameters, I'd rate it as a minor annoyance that one can read about in UPDATING (which I updated with the first workaround, don't use J). It certainly isn't worth creating headaches for you over. 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
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 patch to the Binutils maintainers. Binutils 2.10 should be released any day now, so I'll have to do another Buntils import anyway, so I'll get it then. -- -- David ([EMAIL PROTECTED]) 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
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 freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
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
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, and why some > fail. > Bingo. I have AJ set. > P.S. One more beer to phk for putting this functionality into malloc :-) We're going to have one happy phk. Mark me down for one beer. -- Steve 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
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 problem for me. Yes, I know, vendor branch and : all :( If it works, then I think it should be committed in the usual way for this stuff: Filtered through David O'Brien... I've just started a build and will let people know if this works. 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
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 table struct and didn't
add initialization for it into the general hash table struct init func.
This patch cures the problem for me. Yes, I know, vendor branch and
all :(
You need to apply the patch and remake /usr/src/gnu/usr.bin/binutils/libbfd
and then /usr/src/gnu/usr.bin/binutils/ld .
Index: elf.c
===
RCS file: /freebsd/cvs/src/contrib/binutils/bfd/elf.c,v
retrieving revision 1.6
diff -u -r1.6 elf.c
--- elf.c 2000/05/13 16:44:19 1.6
+++ elf.c 2000/05/29 04:58:34
@@ -979,6 +979,7 @@
table->needed = NULL;
table->hgot = NULL;
table->stab_info = NULL;
+ table->dynlocal = NULL;
return _bfd_link_hash_table_init (&table->root, abfd, newfunc);
}
--
Anatoly Vorobey,
[EMAIL PROTECTED] http://pobox.com/~mellon/
"Angels can fly because they take themselves lightly" - G.K.Chesterton
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
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 J that's causing the problem, even without A present. - the assembler generates identical .o files with or without the J option of malloc, so it's really an ld problem. I think you're right, and it expects a zeroed-out malloced memory somewhere. I'll try to hunt for it in spare time. -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton 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
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
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, and why some
fail.
I get these failures on hello world:
int main() { printf("hello world\n"); }
cc -c xxx.c
cc -o xxx xxx.o
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.
So if you have to update your system, don't have /etc/malloc.conf
pointing at AJ:
A All warnings (except for the warning about unknown flags being
set), and failure to allocate memory become fatal. The process
will call abort(3) in these cases.
J Each byte of new memory allocated by malloc(), realloc() or
reallocf() as well as all memory returned by free(), realloc() or
reallocf() will be initialized to 0xd0. This options also sets
the ``R'' option. This is intended for debugging and will impact
performance negatively.
R Causes the realloc() and reallocf() functions to always reallo-
cate memory even if the initial allocation was sufficiently
large. This can substantially aid in compacting memory.
Warner
P.S. One more beer to phk for putting this functionality into malloc :-)
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
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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Internal compiler error: program ld got fatal signal 10
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]:/home/imp/FreeBSD/src/sys/compile/BILLY-CLUB : i386 : : I'll let people know how this works out. Got the same exact results with the PPro 180 as I did on my PIII 500. Definitely not hardware at this point. I think I'm safe in saying that. I'm going to try to upgrade my binutils by hand and see if that helps any. 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
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-CURRENT #33: Sun Apr 30 22:57:58 MDT 2000 [EMAIL PROTECTED]:/home/imp/FreeBSD/src/sys/compile/BILLY-CLUB i386 I'll let people know how this works out. 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
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
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/sys/compile/CELEBRIS-SMP i386 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
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 started at 10:20:27 on 05/28/00 : build finished at 14:39:14 on 05/28/00 : -- : > ld -v : GNU ld version 2.10-anoncvs-2512 (with BFD 2.10-anoncvs-2512) : > as -v : GNU assembler version 2.10-anoncvs-2512 (i386-unknown-freebsdelf5.0) using BFD :version : 2.10-anoncvs-2512 : : In all my tests, I used a normal make buildworld, I never manually : built or installed binutils. Odd. that means that you must have done at least one buildworld with the old binutils. Hmmm. Time to play with the bouncer box to see what I can do with it. 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
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 MAJOR BUMMER if one needed to > update binutils first... 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: -- build started at 10:20:27 on 05/28/00 build finished at 14:39:14 on 05/28/00 -- > ld -v GNU ld version 2.10-anoncvs-2512 (with BFD 2.10-anoncvs-2512) > as -v GNU assembler version 2.10-anoncvs-2512 (i386-unknown-freebsdelf5.0) using BFD version 2.10-anoncvs-2512 In all my tests, I used a normal make buildworld, I never manually built or installed binutils. > Warner -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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
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 first? It sure would be a MAJOR BUMMER if one needed to > update binutils first... > > Warner I have been updating this box by 'make worlds' in 1-2 day intervals recently (for example I did it yesterday but not today) and it worked every time apart from the queue macro bustages, which were easy to fix though. Will try again tomorrow. (esp because I had one report that the SB 64 AWE doesn't work on a kernel from today. I need to verify this.) I got the binutils on the day they were added to the tree but 'make world' was as easy as ever on that day too. (Although I was foolish enough to try to compile a kernel before making an installworld... but it was my fault, I never do this normally I was just not paying attention. It bombed as expected:-) But then I made installworld and everything was fine afterwards.) Just a datapoint...(PII 233 UP here, LX 440 mobo, 64M RAM) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary 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
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 was surprise that no one else had reported this problem : when I sent my original e-mail. It must be restricted to : a specific hardware combination. Must be something specific to our environments. 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
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 then... > > I did a complete buildworld in early May w/o a hitch that worked when > I installed it on my bouncer box. > > Maybe I just need more swap than I have on my machine, or higher > limits for the process building things. Then again, I do have 1/2G of > swap that isn't being used at all during the builds... > Warner, 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). I was surprise that no one else had reported this problem when I sent my original e-mail. It must be restricted to a specific hardware combination. -- Steve Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Fri May 26 09:39:34 PDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/TROUTMASK Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 268435456 (262144K bytes) avail memory = 257748992 (251708K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc0346000. VESA: v1.2, 4096k memory, flags:0x0, mode table:0xc00c1bdf (c0001bdf) VESA: S3 Incorporated. 86C325 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at 7.1 pci0: at 15.0 irq 19 ahc0: port 0xf400-0xf4ff mem 0xf0dff000-0xf0df irq 18 at device 16.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xf0c0-0xf0ff irq 17 at device 17.0 on pci0 xl0: Ethernet address: 00:60:97:98:38:65 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <8 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: This ppc chipset does not support the extended I/O port range...no problem ppc0: at port 0x378-0x37b irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode pps0: on ppbus0 ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port unknown0: at port 0xcf8-0xcff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown1: at port 0x80,0x10-0x1f,0x22-0x2f,0x30-0x3f,0x50-0x5f,0x90-0x9f,0xa2-0xaf,0xb0-0xbf,0xe0-0xef iomem 0xfff8-0x on isa0 unknown2: at iomem 0-0x9,0xe-0xf,0x10-0xfff on isa0 unknown3: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown4: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 unknown5: at port 0x40-0x43 irq 0 on isa0 unknown6: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources npxisa0: at port 0xf0-0xff irq 13 on isa0 unknown7: at port 0x61 on isa0 unknown: can't assign resources unknown8: at port 0x4d0-0x4d1 on isa0 unknown9: at iomem 0xfec0-0xfec0,0xfee0-0xfee00fff on isa0 unknown10: at port 0x620-0x623 on isa0 sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 unknown11: at port 0x200-0x207 on isa0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Waiting 10 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [312700 x 2048 byte records] da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 5.000MB/s transfers (5.000MHz, offset 8) da1: 699MB (1431760 512 byte sectors: 64H 32S/T 699C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled d
Re: Internal compiler error: program ld got fatal signal 10
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 buildworld in early May w/o a hitch that worked when I installed it on my bouncer box. Maybe I just need more swap than I have on my machine, or higher limits for the process building things. Then again, I do have 1/2G of swap that isn't being used at all during the builds... 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
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 if one needed to > update binutils first... 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... -- Marcel Moolenaar mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] tel: (408) 447-4222 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
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 first... 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
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
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/lib/libcrypto.so: file not recognized: File truncated i386/usr/lib/libcurses.so: file not recognized: File truncated i386/usr/lib/libftpio.so: file not recognized: File truncated i386/usr/lib/libgnuregex.so: file not recognized: File truncated i386/usr/lib/libipsec.so: file not recognized: File truncated i386/usr/lib/libipx.so: file not recognized: File truncated i386/usr/lib/libkvm.so: file not recognized: File truncated i386/usr/lib/libm.so: file not recognized: File truncated i386/usr/lib/libmd.so: file not recognized: File truncated i386/usr/lib/libmp.so: file not recognized: File truncated i386/usr/lib/libncp.so: file not recognized: File truncated i386/usr/lib/libncurses.so: file not recognized: File truncated i386/usr/lib/libnetgraph.so: file not recognized: File truncated i386/usr/lib/libpam.so: file not recognized: File truncated i386/usr/lib/libpcap.so: file not recognized: File truncated i386/usr/lib/librpcsvc.so: file not recognized: File truncated i386/usr/lib/libssl.so: file not recognized: File truncated i386/usr/lib/libtermcap.so: file not recognized: File truncated i386/usr/lib/libutil.so: file not recognized: File truncated i386/usr/lib/libwrap.so: file not recognized: File truncated i386/usr/lib/libz.so: file not recognized: File truncated lib/libcom_err/libcom_err.so: file not recognized: File truncated secure/lib/libcrypto/libcrypto.so: file not recognized: File truncated secure/lib/libcipher/libcipher.so: file not recognized: File truncated 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
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 buildworld -k -DNOCLEAN, I get lots of files that are truncated due to this: /usr/obj/home/imp/FreeBSD/src/i386/usr/lib/libcrypto.so: file not recognized: File truncated /usr/obj/home/imp/FreeBSD/src/i386/usr/lib/libssl.so: file not recognized: File truncated /usr/obj/home/imp/FreeBSD/src/i386/usr/lib/libtermcap.so: file not recognized: File truncated etc. 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
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 > : happens quite a bit. > > I'm using a PIII-500 and it is happening to me. This system would > always build world great, but now fails all the time (20 builds) at > exactly the same spot. I don't think this is hardware. > It definitely isn't hardware. This, I believe, is a result of the new binutils. I've narrowed the window to *default date=2000.05.22.00.00.00 <-- build completes. *default date=2000.05.22.12.00.00 <-- ld gets a signal 10. -- Steve 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
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 buildworld process. Buildworld makes all the stuff it needs to > build things, unlike the kernel. I know that it is supposed to do so, I suspect that might not be the case here. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ 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
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 build things, unlike the kernel. 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
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 using a PIII-500 and it is happening to me. This system would always build world great, but now fails all the time (20 builds) at exactly the same spot. I don't think this is hardware. 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
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 three CFLAGS as set in /etc/make.conf : : CFLAGS= : CFLAGS=-O -pipe : CFLAGS=-O2 -pipe : : and the above error occurs. : : Any and all suggestions are welcomed, but it appears to be : a problem with the new binutils. I've seen this as well, and have reported it to the binutils maintainer. I've done the above, plus get rid of -pipe, raise my resource limits to insanely high levels, try it on a fresh tree w/o any of my local hacks, etc. This is building from a 4.0-stable system. I do this because my -stable system is my fileserver/build server and is 3x faster than my bouncer boxes are at building -current and 2x faster than my laptop. It needs to be -stable since it is expected to have long uptimes and I don't want to upgrade all the time. I also need -stable for SO work. 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
In <[EMAIL PROTECTED]>, 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 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 message with a source tree after > > *default date=2000.05.23.00.00.00 Have you tried building and installing the new binutils before compiling the rest of the world? Some assembler files are not compatible with the old binutils. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ 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
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 it > happens quite a bit. > SMP Pentium Pro with 256 MB of memory, and only scsi hardware. Note, ld is getting a signal 10 (SIGBUS) not signal 11 (SIGSEGV), which is the typical crappy hardware signal. Also, I can build the world as long as I use sources older that 23 May 00. This leads me to believe that the new binutils are having some problems. -- Steve 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
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 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 message with a source tree after > > *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 three CFLAGS as set in /etc/make.conf > > CFLAGS= > CFLAGS=-O -pipe > CFLAGS=-O2 -pipe > > and the above error occurs. > > Any and all suggestions are welcomed, but it appears to be > a problem with the new binutils. > > -- > Steve > > To Unsubscribe: send mail to [EMAIL PROTECTED] > 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 it happens quite a bit. Bob -- "I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones." -- Albert Einstein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Internal compiler error: program ld got fatal signal 10
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 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 message with a source tree after *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 three CFLAGS as set in /etc/make.conf CFLAGS= CFLAGS=-O -pipe CFLAGS=-O2 -pipe and the above error occurs. Any and all suggestions are welcomed, but it appears to be a problem with the new binutils. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
