From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1E1xKw-0007Sg-Ty for garchives@archives.gentoo.org; Mon, 08 Aug 2005 02:25:59 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j782NPP2026426; Mon, 8 Aug 2005 02:23:25 GMT Received: from mail.netspace.net.au (thunder.netspace.net.au [203.10.110.71]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j782NNjJ008538 for ; Mon, 8 Aug 2005 02:23:24 GMT Received: from [192.168.0.234] (220-253-105-10.TAS.netspace.net.au [220.253.105.10]) by mail.netspace.net.au (Postfix) with ESMTP id D934F495E5 for ; Mon, 8 Aug 2005 12:23:34 +1000 (EST) Message-ID: <42F6C20C.9000808@burnieanglican.org.au> Date: Mon, 08 Aug 2005 12:23:08 +1000 From: Will Briggs User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] file type not allowed in /usr/lib References: <42F53B6D.1080908@burnieanglican.org.au> <42F5E011.8020907@gentoo.org> In-Reply-To: <42F5E011.8020907@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: fc5a9d8d-ed17-4948-a974-ff82cce35d94 X-Archives-Hash: 4874db589e140065e37f2b49fac52624 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. -- gentoo-amd64@gentoo.org mailing list