This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC PATCH] GCC multilib vs. OS multilib naming
On Fri, Sep 20, 2002 at 11:53:38AM -0400, Daniel Jacobowitz wrote:
> > Using ../lib64 multilib dir for say /usr/lib/gcc-lib/sparc64-linux/3.2.1/
> > directory is not a good idea (it would be shared between say 3.2.1 and
> > 3.3).
> > If the OS=GCC multilib dirs were lib, lib64 and lib64/alt in sparc64-linux
> > case no matter what MULTILIB_DEFAULT is, then all the */lib or libdir
> > prefixes would have to suddenly loose the trailing path component
> > and even the build directory layout would change a lot, requiring big
> > Makefile and config-ml.in surgery.
>
> I think this could be done more easily. We could leave the directories
> the way they are (with ../) and use 3.2.1/lib/ as the tool libdir.
> This would still require separating out what looks for tools vs.
> libraries in tooldir, but it should be much simpler... I don't really
> like the idea of carrying around two different layouts if we don't have
> a technical need to.
It is not about tool libdir only, it is a problem for
boehm-gc, libf2c, libffi, libiberty, libjava, libobjc, libstdc++-v3, zlib
etc. too, but probably some Makefile and config-ml.in could do it.
Jakub