Date: Mon, 10 Oct 2011 08:50:59 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Manfred Antar <null@pozo.com> Cc: "Conrad J. Sabatier" <conrads@cox.net>, 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: <4E9295D3.8080201@zedat.fu-berlin.de> 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 10/10/11 03:18, Manfred Antar 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: >> >>> 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. >> >> Actually, binutils built just fine for me just now without setting >> UNAME_r under current. >> >> -- >> Conrad J. Sabatier >> conrads@cox.net > > 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 gcc45 when built with current. Managed it. Somehow I maneged to build the binutils without setting the UNAME_r kludge. I confused myself and the system. Thanks. I think, watching this is a very good opportunity to learn by doing, how things work. Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E9295D3.8080201>