This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Create multilib installdirs automatically
- To: law at cygnus dot com
- Subject: Re: [PATCH] Create multilib installdirs automatically
- From: Daniel Jacobowitz <drow at false dot org>
- Date: Fri, 15 Oct 1999 09:31:20 -0400
- Cc: gcc-patches at gcc dot gnu dot org
- References: <19990723170844.A9411@drow.res.cmu.edu> <1136.938118127@upchuck.cygnus.com>
On Thu, Sep 23, 1999 at 02:22:07PM -0600, Jeffrey A Law wrote:
>
> In message <19990723170844.A9411@drow.res.cmu.edu>you write:
> >
> > --W/nzBZO5zC0uMSeA
> > Content-Type: text/plain; charset=us-ascii
> >
> > Currently, make install would fail if multilib was enabled but not all
> > the multilib directories already existed. This patch creates them.
> > I'm not entirely sure about the conditionalization I used for
> > $(tooldir)'s multilibs, though.
> ?!? I don't really understand this. The install-multilib rule should have
> created each of the necessary multilib directories.
>
> Under what conditions will the multilib directories not be created by
> the install-multilib rule?
*rummages through his tree and mail archives...*
The failure I saw was in installing multilibbed libiberty.a.n.
If enable_version_specific_runtime_libs is not set, libiberty gets
installed into ${libdir} instead of ${libsubdir}, and ${libdir} has
never had the multilib directories created.
As to why I put it at the bottom of installdirs instead of at the
bottom of install-multilib... to be honest, I don't remember. It seems
more natural to create all the directories needed at once, but if there
was a particular reason it was necessary, it escapes me now.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/