From owner-freebsd-current@FreeBSD.ORG Sun Feb 1 03:00:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5993610657BD for ; Sun, 1 Feb 2009 03:00:51 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 29D818FC1A for ; Sun, 1 Feb 2009 03:00:51 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.2/8.14.2) with ESMTP id n112xeeT094506; Sat, 31 Jan 2009 18:59:40 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.2/8.14.2/Submit) id n112xdvV094505; Sat, 31 Jan 2009 18:59:39 -0800 (PST) (envelope-from obrien) Date: Sat, 31 Jan 2009 18:59:39 -0800 From: "David O'Brien" To: Pegasus Mc Cleaft Message-ID: <20090201025939.GD83330@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Pegasus Mc Cleaft , "O. Hartmann" , Anton Shterenlikht , freebsd-current@freebsd.org References: <497064C6.5070807@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Anton Shterenlikht , freebsd-current@freebsd.org, "O. Hartmann" Subject: Re: Alternatives to gcc (was Re: gcc 4.3: when will it become standard compiler?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2009 03:00:51 -0000 On Fri, Jan 16, 2009 at 11:46:29AM -0000, Pegasus Mc Cleaft wrote: > In my, probably ill informed opinnion, the problem we are facing is not > a C compiler problem, its an assembler problem. We can install a better C > compiler of our choice through the ports, but its the base assembler & > linker that lets us down because it dosent know about modern CPU opcodes > and registers (IE: SSE4.x). .. > gcc43 is fairly painless through the ports, but this is of limited use as > it will use the base assembler, linker, et al. Even if you install, as I > have, the latest binutils from GNU, it will locate /usr/bin/as before > /usr/local/bin/as. If you set all the enviroment varables (AR, AS, NM, ...) > before you do the build, you run into other problems with finding the > bootstrap files later due to the naming problems between > "x86_64-obrien-freebsd" and the auto-generated "x86_64-unknown-freebsd8.0" > from the GNU configure. In short, I found upgrading the dev-chain a real > nightmare. Its not that bad. I've created several cross toolchains in the past. For those you specify which 'as' and 'ld' to use - how else do you think they work. I don't think you configured your GCC properly if you cannot get it to use some binutils from /usr/ports. In fact when installing GCC on Solaris GCC strongly prefers (or use to) gas and gld to Sun's as and ld. Just tweak that configure logic. -- -- David (obrien@FreeBSD.org)