-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/27/2012 06:49 AM, Duncan wrote: > Rick \"Zero_Chaos\" Farina posted on Fri, 27 Jul 2012 01:44:47 -0400 as > excerpted: > >> * Messages for package app-emulation/emul-linux-x86-baselibs-20120520: >> >> * QA Notice: Missing soname symlink(s): >> * >> * usr/lib32/libgnuintl.so.8 -> preloadable_libintl.so >> * >> * QA Notice: Missing soname symlink(s): >> * >> * usr/lib32/libgnuintl.so.8 -> preloadable_libintl.so >> * >> * QA Notice: Files built without respecting CFLAGS have been detected >> * Please include the following list of files in your report: >> * /lib32/libpam.so.0.83.1 * /lib32/libgpm.so.1.20.0 > > > I'm unsure whether you realize that app-emulation/emul-linux-x86-* are > special-case and I'm missing something obvious (like some indication that > you're simply trying to shutup the warnings in this case), or whether > it's you missing the obvious, but just in case it's the latter I'll risk > publicly exposing the fact that I missed the former... =:^\ > > The emul-linux-x86-* packages are pre-compiled 32-bit binaries there for > the convenience of amd64 multilib users who don't wish to run the 32-bit > chroot and separate 32-bit stage-based PM installation otherwise > necessary (in the absence of true multi-arch package-manager support) in > ordered to build the 32-bit libraries needed by some of their presumably > proprietary 32-bit-binary-only apps. > > As such, they'll NEVER respect local CFLAGS, since they're not built > locally.
There are various QA_something_something which silence the warning, I'm not saying they have to actually fix the cflags issue but I want to not get warned when I shouldn't, like on prebuilt stuff like this. > > Similarly, various so-name symlinks (plus headerfiles, *.pc files, etc) > are omitted as they're only necessary when building reverse-deps, and > these are binary-only packages not intended to be built against, and > including these files would only increase the likelihood of conflict when > trying to build against the 64-bit versions. > I actually didn't intend to paste that error, I was only trying to get the cflags ones, but since you mentioned it, I'm sure there is a QA_something to silence that error or, you know, dosym. Users shouldn't see QA warnings, those are for devs to fix before committing. Thanks, Zero > As hinted above, to do the normal gentoo-ish build for the 32-bit version > of these libs on a 64-bit system, you follow the amd64 32-bit chroot > guide, installing a separately tracked and configured 32-bit x86 "stub > system" from 32-bit stages, thus ensuring all the necessary 32-bit > dependencies are available, etc, altho this 32-bit stub need not contain > system services, etc, unless you want to actually be able to boot to it, > since those are generally provided by the 64-bit side. Since that's a > LOT of extra work for the set of basic 32-bit libs that's all many will > use, the emul-linux-x86-* packages are available as a convenient (and > default) alternative for those that prefer to use them. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQEtIXAAoJEKXdFCfdEflKN+gP+gMzVC/1tz0rxy47NUCLYKbt c+aGqZzdobhGgvClD/HVSzBpymE9uiZl5oQSXxXajRxC3OauAQNbPtmnGxIqIjTJ 19a9sYOLC0TlPjjoa5/2SV5bMz/po2DPntpNB248phoh9v3xrvCvof1z53+58Y9V bufePhH+oCDg906QBziYp6qmuZ+2SM8dmXCDArdoVnH55SoWfDwCmcYHhzf2GPyh BizQo9dlH1/RZdM0TCCeZEXw0oyf/XlSDwTvig4qSLjtWvV2mZ65AfPnXl1qPZRR rzPoAQzUi2j1xgy9DYIouzG26PiMolaw0dOII6B04KYi+CZJqWBKLNFdbkv4XJc5 6xwLXxo3foVzpg5wk2CXHu5vPu/p0vY8/CrziDaFKYz5GyWiCSqAiWW6lV4tM1q5 3/H3ozKYSRKKn+L5iJ8+zhXfR5HQTy6TJrIoIJRD1x2xqsIjlMBqO2AMrHaf+aAw X3JzemyZCWcJkRGUoJIMeKGUOCMMVDeDSP4H49MF7211LxOue1IG9TV27lbywE6e tPFPRlyTE5iJSbfSWHslTRfugOOwvBEaBGZ3ZwO4LkUaH9/yH3LWYRNjoaH693hX sv7RE+aU4yQ9NYUUX5veXIh5Ip7JI9oA1PhrTXmPEnZzJkJXv6X4rlGzz3DgwTbV xKmL6hW+h0IVr3LzaUKq =WAZa -----END PGP SIGNATURE-----
