From owner-freebsd-current Sun May 28 21:43:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5E10A37BA76; Sun, 28 May 2000 21:43:24 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA35387; Sun, 28 May 2000 22:43:22 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA04684; Sun, 28 May 2000 22:43:08 -0600 (MDT) Message-Id: <200005290443.WAA04684@harmony.village.org> To: obrien@freebsd.org Subject: Re: Internal compiler error: program ld got fatal signal 10 Cc: Anatoly Vorobey , current@freebsd.org In-reply-to: Your message of "Sun, 28 May 2000 21:39:53 PDT." <20000528213953.C45049@dragon.nuxi.com> References: <20000528213953.C45049@dragon.nuxi.com> <20000529050529.A10617@happy.checkpoint.com> <200005282312.RAA36480@harmony.village.org> <20000529050529.A10617@happy.checkpoint.com> <200005290232.UAA69052@harmony.village.org> Date: Sun, 28 May 2000 22:43:08 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000528213953.C45049@dragon.nuxi.com> "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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message