Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Oct 2009 10:53:35 -0400
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: binutils
Message-ID:  <44hbu7mhao.fsf@lowell-desk.lan>
In-Reply-To: <20091010103623.11ed0154@scorpio.seibercom.net> (Jerry's message of "Sat, 10 Oct 2009 10:36:23 -0400")
References:  <permail-200910101345391e86ffa800007f68-a_best01@message-id.uni-muenster.de> <20091010103623.11ed0154@scorpio.seibercom.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Jerry <gesbbb@yahoo.com> writes:

> On Sat, 10 Oct 2009 15:45:39 +0200 (CEST)
> Alexander Best (alexbestms@math.uni-muenster.de) replied:
>
>>there's a project called binutils in p4 but i don't know anything
>>about it (version, status, etc.). the problem with binutils from the
>>portsdir is that even when it's installed gcc still uses the the
>>base-binaries because gcc is statically linked. so in order to use the
>>binutils from the ports dir you also have to install a gcc port (which
>>gets linkey dynamically).
>>
>>a very dirty workaround is to install binutils from the ports, rename
>>the base binary you don't want to use anymore and instead create a
>>link to /usr/local/bin/*.
>>
>>here's an example. this way i could build mplayer with sse3 support.
>>although the base gcc (4.2.1 in my case running 9-current) supports
>>sse3, the base GNU assembler version (2.15) doesn't.
>>
>>what i did was to install the binutils port,
>>`mv /usr/bin/as /usr/bin/as_old` and `ln
>>-s /usr/local/bin/as /usr/bin/as`.
>>
>>now the base gcc picks up the new GNU assembler binary.
>>
>>cheers.
>>alex
>>
>>
>>oh...and i agree: binutils should be updated. actually a lot of base
>>code needs to be updated. some of it hasn't been touched for over a
>>decade. ;)
>
> Is FreeBSD-8.0 also going to continue to use the older version {GNU
> assembler 2.15 [FreeBSD] 2004-05-23} or are they updating to the latest
> version. If the obsolete version is all ready causing compiler
> problems, it would seem like the logical thing to do.

Unfortunately, it's under an unacceptable license.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
		http://be-well.ilk.org/~lowell/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44hbu7mhao.fsf>