Simon Stelling wrote:
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.
Excellent. I learn some more detail just from that. Thanks.
I've got my head pretty much around what multilib _should_ do
eventually. (Duncan's verbosity in the past has helped with that :-)
especially in the many threads on the 2005.0 changeover).
I'm always keen on knowing the detail of where things are up to though -
both wrt 2005.1 and dual-bitness of portage. If Duncan's roadmap (in
his post) is an invention does that mean that there isn't one?
I'm hanging out for portage becoming dual-bitness aware. In the 'other
issue' - the quest to make all ebuilds multilib-friendly - is there a
standardised process for the amd64 mob to lodge
"needs-to-be-multilibbed" bug reports?
W.
--
[email protected] mailing list
