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: DJ Delorie <dj at redhat dot com>
- To: hjl at lucon dot org
- 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 15:21:03 -0500
- 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> <200202041951.g14JpsS20809@greed.delorie.com> <20020204120728.A17054@lucon.org>
> That is the toplevel Makefile. For the in-tree build, srcdir is always
> ".". You check if [ "$(srcdir)" = "." ] to see if it is an in-tree
> build. If it is, you have to duplicate the source tree for the build
> directory. Otherwise, you don't need to duplicate the source tree. You
> can use VPATH in this case. Did I miss something?
Ok, I thought you meant that was what you were seeing in libiberty.
That code is copied verbatim from the target code, and the target
libiberty builds. Why is the build code different?
> configure: error: can not find install-sh or install.sh in ./.. ././..
> make: *** [configure-build-libiberty] Error 1
This message indicates that $(srcdir) is "./." for the
build-libiberty, which is wrong. It should include ".." somewhere.
Probably "../../libiberty".