public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: multilib and the compatibility to singlelib
Date: Tue, 20 Oct 2009 21:27:14 -0400	[thread overview]
Message-ID: <200910202127.15192.vapier@gentoo.org> (raw)
In-Reply-To: <4ADE21F6.4000700@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 1470 bytes --]

On Tuesday 20 October 2009 16:47:50 Jonathan Callen wrote:
> Mike Frysinger wrote:
> >> The problem was that Gentoo's early amd64 implementation predated this
> >> standardization, and we had chosen the other way.  While we've defaulted
> >> to lib64 for 64-bit libs for years, it has never been considered
> >> anything but experimental to break the lib --> lib64 link.  AFAIK stable
> >> baselayout still doesn't get its libdir usage consistent, putting files
> >> in one but actually calling them using the other path, and boot breaks
> >> in various frustrating ways if lib and lib64 are not the same directory.
> >> Openrc gets it better now, but I'm not sure it's all fixed either -- it
> >> certainly wasn't last time I tried breaking the link.
> >
> > your "AFAIK" isnt useful.  there are no open bugs about either version
> > and people assume that it's doing the right thing.
> 
> Personally, I do have a ~amd64 Gentoo chroot with LIBDIR_x86="lib".
> There is only one place that I've found that it is still broken, namely
> one line in toolchain.eclass (patch attached). I've been meaning to file
> a bug for quite a while now, but never got around to it.

off the top of my head, that doesnt really look like a correct fix.  please 
open a bug with info on what you're actually doing.

plus, your LIBDIR_x86 isnt really respected.  there are places where 
lib32/lib64 are hardcoded when modifying gcc/binutils (patch or sed).
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-10-21  1:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 13:06 [gentoo-dev] RFC: multilib and the compatibility to singlelib Michael Haubenwallner
2009-10-20 14:19 ` [gentoo-dev] " Nikos Chantziaras
2009-10-20 15:29 ` [gentoo-dev] " Thomas Sachau
2009-10-20 16:25   ` [gentoo-dev] " Duncan
2009-10-20 17:45     ` Mike Frysinger
2009-10-20 20:47       ` Jonathan Callen
2009-10-21  1:27         ` Mike Frysinger [this message]
2009-10-20 18:16 ` [gentoo-dev] " Mike Frysinger
2009-10-21 11:34   ` Michael Haubenwallner
2009-10-26 12:12     ` Mike Frysinger
2009-10-27 10:19       ` Michael Haubenwallner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200910202127.15192.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox