Date: Sat, 10 Oct 1998 18:01:36 +0800 From: Peter Wemm <peter@netplex.com.au> To: Bruce Evans <bde@zeta.org.au> Cc: rnordier@nordier.com, committers@FreeBSD.ORG, rnordier@FreeBSD.ORG, skynyrd@opus.cts.cwu.edu Subject: Re: cvs commit: src/sys/boot/i386 Makefile Message-ID: <199810101001.SAA15165@spinner.netplex.com.au> In-Reply-To: Your message of "Sat, 10 Oct 1998 20:08:04 %2B1000." <199810101008.UAA22994@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote:
> >> 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.
>
> No, ideal for changing the default a whole subtree is to put the change
> in Makefile.inc at the top of the tree and inherit this recursively.
> The MAKEFLAGS hack fails for normal builds (when `make' is run in a leaf
> directory) because it doesn't affect the current invocation of make.
Putting it in Makefile.inc won't always work, it is "too late".
Makefile.inc is included by things like bsd.prog.mk, so it's pulled in
very late.
> Only the setting of LIBDIR in bsd.own.mk is wrong if a Makefile[.inc]
> changes OBJFORMAT. This is fairly harmless except for installng libraries.
And dependencies.. It could mean that binaries were depending on the
wrong libraries. If the environment format was a.out, and a makefile
reset it to (say) elf, then you end up with your elf binaries depending on
/usr/lib/aout/libfoo.a etc.
> Bruce
Cheers,
-Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810101001.SAA15165>