Date: Tue, 19 May 2009 12:45:48 +0100 From: xorquewasp@googlemail.com To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: bootstrapping gnat GCC on amd64 Message-ID: <20090519114548.GA8610@logik.internal.network> In-Reply-To: <Pine.GSO.4.64.0905181828110.20749@sea.ntplx.net> References: <20090505005128.GA4519@logik.internal.network> <Pine.GSO.4.64.0905042052320.16666@sea.ntplx.net> <20090505022151.GA32477@logik.internal.network> <Pine.GSO.4.64.0905042224180.16666@sea.ntplx.net> <20090506140325.GA69468@logik.internal.network> <Pine.GSO.4.64.0905061043420.26946@sea.ntplx.net> <20090506152222.GC69468@logik.internal.network> <20090508211022.GA37475@logik.internal.network> <20090518084831.GA95354@logik.internal.network> <Pine.GSO.4.64.0905181828110.20749@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-05-18 18:36:15, Daniel Eischen wrote: > Well, I used a newer binutils on sparc when I did the original > port. Once I built the cross compiler and binutils toolset, > I was done with it. After the native compiler is built using > the cross tools, you should be able to rebuild the native > compiler _again_ but this time with the system (amd64) > binutils. I probably should point out that I don't think this is the case anymore. GCC apparently detects what capabilities the currently selected binutils have so when the first native compiler has been compiled using the cross, it will emit code that can't be assembled using the system binutils (because it uses features from the new binutils that aren't supported by the older system ones). In other words, you can't rebuild the native compiler using the system binutils. If the worst comes to the worst, I can create a dependency on the devel/cross-binutils port. xw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090519114548.GA8610>