[PATCH] Configure outside of source tree

Kyle Grieb grieb.kyle@gmail.com
Tue Mar 22 22:00:00 GMT 2011

2011.03.22 17:04+0100 yann e. morin
> Trevor, Kyle, All,
> On Tuesday 22 March 2011 16:22:04 Trevor Woerner wrote:
> > What is your expected usage scenario?

Once re-submitted, to be able to issue 'configure' and thus 'make'
outside of the source tree.

> Basically, enable out-of-tree build of crosstool-NG, for example, in case
> the source tree is RO, or on an NFS share, or...
> Not too sure it would be very important in the crosstool-NG case. For much
> bigger projects (gcc. linux kernel, glibc and so on), it does make sense,
> but for crostool-NG, really?
> > $ make
> > make: *** No targets specified and no makefile found.  Stop.
> > $ ls
> > That's not what I was expecting :-)
> Yep, there are issues with the patch. Kyle already said he'd send an updated
> version. Kyle?

Noticed this, at the time I was only configuring outside of tree and
building inside. 

> > > This will allow 'configure' to be called outside of the sources tree.
> > > Example: /tmp/foo/crosstool-n/configure
> > I'm guessing this is a matter of doing things differently, but I'm not
> > sure what's gained by being able to configure outside the source tree
> > if I then have to move back to the source tree to build (or use a -C
> > cmdline option to 'make').

Sorry for the false hope. Fixing.

The first patch was just to be able to configure outside of the tree and
build inside of the tree.  I am working on a solution to build and
configure outside of the tree, I will patch 'Makefile.in' and 'configure'. I
should have a patch ready to be submitted by the 28th.

Reason for this is more personal than anything, I prefer building
everything outside of source.
Kyle Grieb

For unsubscribe information see http://sourceware.org/lists.html#faq

More information about the crossgcc mailing list