Date: Sat, 16 Dec 2000 13:40:46 +1100 From: Benno Rice <benno@FreeBSD.org> To: Marcel Moolenaar <marcel@cup.hp.com> Cc: Bruce Evans <bde@zeta.org.au>, freebsd-current@FreeBSD.ORG Subject: Re: Patch to allow overriding of nm in lorder, genassym.sh Message-ID: <20001216134045.A47731@rafe.jeamland.net> In-Reply-To: <3A39DFB8.2636725A@cup.hp.com>; from marcel@cup.hp.com on Fri, Dec 15, 2000 at 01:09:12AM -0800 References: <20001213224645.A16171@rafe.jeamland.net> <Pine.BSF.4.21.0012142237280.3687-100000@besplex.bde.org> <20001214234559.B29875@rafe.jeamland.net> <3A39DFB8.2636725A@cup.hp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 15, 2000 at 01:09:12AM -0800, Marcel Moolenaar wrote: > Benno Rice wrote: > > > > > genassym.sh and lorder.sh are also missing support for the -aout/-elf > > > command line option, and this breaks building of kernels in a non-native > > > object format. I think the correct fix is is to set OBJFORMAT before > > > running shell scripts that run binary utilities, not to clutter the > > > shell scripts with code to select the correct binarary utility. > > > > This doesn't fix my problem though. The problem I'm facing is that the > > command 'nm' is hardcoded into both genassym.sh and lorder.sh, when I > > need to run 'powerpc-elf-nm'. Even if we were to move that piece of config > > into OBJFORMAT, it'd still require some kind of magic in the scripts. > > Having nm(1) hardcoded is not a problem if you can cross build. I assume > our toolchain has support for the powerpc and thus will build and > install nm(1) in the object tree. Yes, if cross building doesn't work > yet, we're forced to revert to hackery because we don't have sufficient > flexibility and all we basicly need is a prefix, right? (for example > "powerpc-elf-" or "ia64-unknown-linux-") AFAIK, there is no powerpc support in our toolchain yet. It's on obrien's todo list (and if it isn't, I'll put it there =)). As to the use of a prefix, I just thought it'd be easier to be able to completely override the name of the binary we're using in the same way that I could do: setenv CC /usr/local/bin/ultra-funky-c-compiler-pro and have it work. -- Benno Rice benno@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001216134045.A47731>