Re: [gentoo-amd64] file type not allowed in /usr/lib

[Simon Stelling <blubb@gentoo.org>]

Hi,

Will Briggs wrote:
> !!! ERROR: media-gfx/skencil-0.6.16 failed.
> !!! Function dyn_install, Line 1114, Exitcode 0
> !!! File
> /var/tmp/portage/skencil-0.6.16/image///usr/lib/skencil-0.6.16/Lib/paxtkinter.so 
> matches a file type that is not allowed in /usr/lib
> !!! If you need support, post the topmost build error, NOT this status 
> message.

This means that there are 64bit shared objects going to /usr/lib instead 
of /usr/lib64, which is wrong, but currently not really a bug, since 
/usr/lib is a link to /usr/lib64.

> So if anyone can help with a fix, please let me know.

Just remove 'multilib-strict' from your FEATURES.

> The _question_ relates to the fact that I've seen this sort of error a 
> number of times, but by the time I come across it it's been bugged and 
> fixed and the next emerge sync fixes it.  Can someone let me know what 
> the issue is here - (mainly so I can get a handle on hacking my own 
> fixes when bug reports go unanswered)  Why can't a .so file be placed in 
> /usr/lib?

It can, but it shouldn't. We want 64bit .sos to go to (/usr)/lib64 and 
32bit to (/usr)/lib32, because *taking a deep breath*:

Generally, we want to provide a fully multilib-capable system. That 
means that you will be able to compile every application for 32bit or 
64bit, depending on your mood ;). 32bit applications require 32bit 
libraries, otherwise they can't be linked against each other, same 
(obviously) for 64bit apps/libs. Now imagine you want appfoo (32bit) and 
appbar (64bit), both depending on libfoobar. So you need libfoobar twice 
-- once 64bit and once 32bit.

Now, if libfoobar would get installed to /usr/lib instead /usr/lib32 and 
/usr/lib64, it'd obviously overwrite itself. Depending on what you 
install first, appfoo or appbar will break, as they both require 
installing libfoobar. Also, if you would emerge -C appfoo && emerge 
depclean, appbar wouldn't work anymore, because they both provide 
exactly the same files.

The simple solution to this is making two directories and making sure 
that no 64bit shared object goes anywhere else than to (/usr)/lib64, and 
vice versa.

Regards,

-- 
Simon Stelling
Gentoo/AMD64 Operational Co-Lead
blubb@gentoo.org
-- 
gentoo-amd64@gentoo.org mailing list