Taming GNU make

• Previous message: Michael Heiming: "Re: LILO question"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Sat, 23 Oct 2004 18:26:06 +0000

Hey,

I've become far too used to depending on the GNU make tool to do all of
the dirty work building packages and want to know how to fully control
the process of building from source:-

eg. during a "normal" build I might do something along the lines of

patch -Np1.....
./configure --sysconfdir= --prefix=
make DESTDIR=... && make DESTDIR=... install
strip -debug/uneeded [as appropriate]
checkinstall....
installpkg....

Whilst this is a workable system, I really want to know precisely what
libraries are being used and what compiler and linker are being invoked.
I'd also like to control the target architecture and host.

What I would like to do is control more the build process by

1. ensuring I use a specific set of tools to perform compilation + linking
   (eg. use a specific toolchain)

2. building using shared or static libraries found in a specific path only

3. build to a specific CHOST (eg. build for a Pentium 1 machine on a K6-2)
   (I don't want to cross-compile to different platforms, only i386)

4. Be able to link an entire package statically

I've experimented with LIBPATH, LDFLAGS, CFLAGS and CHOST but can't seem
to get a combination that works - I also don't know whether to apply them
as environment variables, put them in the commands or do something else.

Any assistance or a link to documentation you may know of would be
gratefully appreciated,

With thanks,
Dave

<Have set Followup-to: alt.os.linux>

-- 
David Green (mail.david@dsl.pipex.com)
Hands up for human rights!
http://www.amnesty.org

• Previous message: Michael Heiming: "Re: LILO question"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]