Date: Sun, 9 Oct 2011 18:47:56 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Manfred Antar <null@pozo.com> Cc: "Conrad J. Sabatier" <conrads@cox.net>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: FreeBSD 10.0-CURRENT: messed up the ports and system (gcc46 won't compile) and need to repair - how? Message-ID: <A9C88637-0DC8-49BA-A513-06F5358063BC@gmail.com> In-Reply-To: <201110100118.p9A1IJ0K005636@pozo.com> References: <4E919228.8010708@zedat.fu-berlin.de> <201110091548.p99FmpF4018785@pozo.com> <20111009135735.3f5fe1c1@cox.net> <201110100118.p9A1IJ0K005636@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 9, 2011, at 6:18 PM, Manfred Antar <null@pozo.com> wrote: > At 11:57 AM 10/9/2011, Conrad J. Sabatier wrote: >> On Sun, 09 Oct 2011 08:48:46 -0700 >> Manfred Antar <null@pozo.com> wrote: >>=20 >>> Did you rebuild ports/devel/binutils after change to 10.0 current. >>> I was having same problem with gcc45 , then i rebuilt binutils with >>> uname_r 9.0-Current and it went away. >>=20 >> Actually, binutils built just fine for me just now without setting >> UNAME_r under current. >>=20 >> --=20 >> Conrad J. Sabatier >> conrads@cox.net >=20 > Built fine for me too. But when I tried to compile gcc45 no go > recompiled binutils with uname_r 9.0-CURRENT, And gcc45 built fine. > so my assumption was that something gets messed up with the binutils and g= cc45 when built with with current. Some branding info is indeed embedded in the Gnu toolchain (look at gcc -dum= pspecs, etc). -Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A9C88637-0DC8-49BA-A513-06F5358063BC>