Date: Mon, 09 Jun 2003 17:20:58 -0500 From: Jeremy Messenger <mezz7@cox.net> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: freebsd-current@freebsd.org Subject: Re: Buildworld failed by binutils/bfd/targets.c:1092.. Message-ID: <oprqito8bb8ckrg5@smtp.central.cox.net> In-Reply-To: <20030609214501.GB7597@ns1.xcllnt.net> References: <oprqiqtkwu8ckrg5@smtp.central.cox.net> <20030609214501.GB7597@ns1.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Jun 2003 14:45:01 -0700, Marcel Moolenaar <marcel@xcllnt.net>
wrote:
> On Mon, Jun 09, 2003 at 04:18:46PM -0500, Jeremy Messenger wrote:
>> I just CVSup'ed at the phk's lastest committed on UPDATING/CDD stuff. I
^^^I mean,
CCD..
>> did the buildworld and it has been failed.
>>
>> ==============================
>> /usr/src/contrib/binutils/bfd/targets.c -o targets.o
>> In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
>> targmatch.h:7:1: null character(s) ignored
>> targmatch.h:12:1: null character(s) ignored
>> targmatch.h:16:1: null character(s) ignored
>> targmatch.h:20:1: null character(s) ignored
>> targmatch.h:24:1: null character(s) ignored
>> targmatch.h:28:1: null character(s) ignored
>> targmatch.h:32:1: null character(s) ignored
>> targmatch.h:36:1: null character(s) ignored
>> targmatch.h:40:1: null character(s) ignored
>> targmatch.h:44:1: null character(s) ignored
>> targmatch.h:48:1: null character(s) ignored
>> targmatch.h:51:1: null character(s) ignored
>> targmatch.h:55:1: null character(s) ignored
>> targmatch.h:58:1: null character(s) ignored
>> targmatch.h:62:1: null character(s) ignored
>> [...]
>> targmatch.h:2024:1: null character(s) ignored
>> targmatch.h:2028:1: null character(s) ignored
>> targmatch.h:2033:1: null character(s) ignored
>> targmatch.h:2037:1: null character(s) ignored
>> *** Error code 1
>> Stop in /usr/src/gnu/usr.bin/binutils/libbfd.
>> *** Error code 1
>> Stop in /usr/src/gnu/usr.bin/binutils.
>> *** Error code 1
>> ==============================
>>
>> Any hint?
>
> Broken sed(1), I think. Has been fixed last week.
Yes, I remember it's fixed but I didn't remember/know that broke sed caused
this..
> If you did a -DNOCLEAN build, don't. Otherwise, build and install sed
> first.
Build and install sed first did the trick. Thanks!
Cheers,
Mezz
--
bsdforums.org 's moderator, mezz.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oprqito8bb8ckrg5>