Date: Sat, 10 Oct 1998 11:30:19 +0200 (SAT) From: Robert Nordier <rnordier@nordier.com> To: peter@netplex.com.au (Peter Wemm) Cc: rnordier@nordier.com, skynyrd@opus.cts.cwu.edu, rnordier@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: cvs commit: src/sys/boot/i386 Makefile Message-ID: <199810100930.LAA10470@ceia.nordier.com> In-Reply-To: <199810100309.LAA13373@spinner.netplex.com.au> from Peter Wemm at "Oct 10, 98 11:09:41 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Wemm wrote:
> Robert Nordier wrote:
> > Yes. The problem is that make world is lumping the old and new
> > boot code together as "legacy boot", but they require a different
> > OBJFORMAT.
>
> By the way, it is possible to set $OBJFORMAT (the environment variable) in
> a Makefile. This might be an idea for sys/boot/Makefile and
> sys/i386/boot/Makefile
>
> Is this worth doing? For example:
> [ ... ]
That's a useful technique I wasn't aware of.
For /sys/i386/boot, which is completely oriented to a.out, it seems
the ideal solution.
For /sys/boot/i386, which can output executables in both formats
(where they aren't flat binary files) I suppose OBJFORMAT really
means "Make the actual /boot/loader binary in this format".
(I've gone with another of your suggestions, and the new boot2
supports both a.out and ELF, which means an ELF /boot/loader binary
is feasible.)
So for /sys/boot/i386/Makefile, I suggest we do something like:
.MAKEFLAGS: BTXLDFMT=${OBJFORMAT} OBJFORMAT=elf
Thanks.
--
Robert Nordier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810100930.LAA10470>