Subject: Re: NetBSD/sparc now using new toolchain
To: None <firstname.lastname@example.org>
From: Markus W Kilbinger <email@example.com>
Date: 11/04/2001 01:35:57
>>>>> "Jason" == Jason R Thorpe <firstname.lastname@example.org> writes:
Jason> Today, with some help from Martin Husemann (who tested and
Jason> helped get the profiling support working with the new
Jason> compiler), I switched the sparc port to the new toolchain
Jason> (i.e. USE_NEW_TOOLCHAIN=yes). Both the sparc and sparc64
Jason> port now use the new toolchain, which is based on GCC
Jason> 2.95.3 and Binuitls 2.11.2.
Jason> The main upshot of this is that cross-builds of
Jason> NetBSD/sparc (with the exception of full snapshots due to
Jason> host tool issues) is now quite trivial, so if you have a
Jason> fast PC and want to use it to build binaries for your
Jason> slower SS2, you can do that (I'm using my laptop to build
Jason> the world for my SPARC Classic now :-)
One problem I ran into when cross compiling (i386 -> sparc) was the
use of /dev/vnd0c instead /dev/vnd0d on my i386 build system during
image creation. How to avoid this?
Will src/build.sh be the start point for any kind of (cross)
compilation, even for 'make build'?