[Top] [All Lists]

Re: Probs while building xfsdump

To: Eric Sandeen <sandeen@xxxxxxx>, Michael Wahlbrink <mimi.ka@xxxxxx>
Subject: Re: Probs while building xfsdump
From: Nathan Scott <nathans@xxxxxxx>
Date: Wed, 14 Aug 2002 10:25:05 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1029270924.14229.35.camel@xxxxxxxxxxxxxxxxxxxxxx>
References: <3D590942.3000309@xxxxxx> <1029250612.14205.3.camel@xxxxxxxxxxxxxxxxxxxxxx> <1029251934.14229.8.camel@xxxxxxxxxxxxxxxxxxxxxx> <3D592D6B.9050509@xxxxxx> <3D59643E.3040408@xxxxxx> <1029270924.14229.35.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.4i
On Tue, Aug 13, 2002 at 03:35:24PM -0500, Eric Sandeen wrote:
> Ugh...
> Well, it seems that you want to put things in "normal" places, so...
> If you skip the autoconf; ./configure steps, the Makefile will do this
> for you, and feed values to configure that do all the "right" things.
> You can look at each Maiefile under the $(CONFIGURE): target to see what
> it's going to do.

This is the best approach - if you want your own install
locations, start with these defaults and work backwards.

> hopefully that will get you going until this is sorted out a bit.

Basically you need to tell the build system where to put things,
otherwise you get the configure defaults.  For packages like
xfsprogs, there is a need to install to several places that do
not have "standard" configure targets, so I had to get creative
with using the targets configure does provide - in particular,
we want to differentiate where runtime libs go from where devel
libs go - there is no simple way to do that, and so the defaults
we get are a bit wacky for that one (runtime libs use libdir, so
devel libs ended up in libexecdir).



<Prev in Thread] Current Thread [Next in Thread>