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