[patch] binutils current: libiberty/configure and --with-build-subdir

H . J . Lu hjl@lucon.org
Tue Feb 5 11:24:00 GMT 2002


On Tue, Feb 05, 2002 at 10:27:56AM -0800, H . J . Lu wrote:
> On Tue, Feb 05, 2002 at 11:29:42AM -0500, DJ Delorie wrote:
> > 
> > These changes seem wrong to me.  The point of them is to avoid trying
> > to auto-detect certain things because we're building a target library,
> > but for the build libiberty we are guaranteed to have a working
> > toolchain and we can safely autodetect everything.
> > 
> 
> How about this patch? We just need to get the right "libiberty_topdir".
> We don't need to guess the build machine name since it is passed to
> libiberty. The only thing missing is the toplevel "config" directory
> which may be needed by libiberty. I have a kludge for that also.
> 

libiberty only needs the toplevel "config" directory for shared library.
But I don't think we should do it for the build library since it is
only used during build and is not the part of the final binaries.


H.J.



More information about the Binutils mailing list