This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: [patch] binutils current: libiberty/configure and --with-build-subdir
- From: "H . J . Lu" <hjl at lucon dot org>
- To: DJ Delorie <dj at redhat dot com>
- Cc: macro at ds2 dot pg dot gda dot pl, binutils at sources dot redhat dot com,gcc-patches at gcc dot gnu dot org, zack at codesourcery dot com
- Date: Mon, 4 Feb 2002 11:49:34 -0800
- Subject: Re: [patch] binutils current: libiberty/configure and --with-build-subdir
- References: <Pine.GSO.3.96.1020204171204.5750G-100000@delta.ds2.pg.gda.pl> <20020204085738.A13941@lucon.org> <200202041839.g14IdFI19732@greed.delorie.com> <20020204114134.A16584@lucon.org>
On Mon, Feb 04, 2002 at 11:41:34AM -0800, H . J . Lu wrote:
> On Mon, Feb 04, 2002 at 01:39:15PM -0500, DJ Delorie wrote:
> >
> > You can't just change the option; --with-target-subdir causes changes
> > in what's inside libiberty.a and triggers the multilib code.
> > Libiberty really needs to properly understand --with-build-subdir if
> > you want it to work that way.
> >
> > However, try configuring in a different directory and use an absolute
> > path to configure, and see if that makes a difference.
> >
> > Another consideration is that $srcdir may be improperly set, which
> > would need to be fixed first (or also).
>
> The problem is
>
> if [ "$(srcdir)" = "." ] ; then \
> if [ "$(BUILD_SUBDIR)" != "." ] ; then \
> if $(SHELL) $$s/symlink-tree $${topdir}/$${dir} "no-such-file"
> ; then \
>
> It is bogus. You only duplicate the sub tree. However, to configure
> that directory, you also need install-sh, config.guess, config.sub, ...
> from the top level. Basically, you may have to duplicate the whole tree
> under $(BUILD_SUBDIR). But do you really want to do that?
If noone is going to fix the in-tree build for build != host, shouldn't
we issue an error message during configure?
H.J.