-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/08/13 01:41 PM, Alexis Ballier wrote: > On Fri, 09 Aug 2013 13:36:31 -0400 Ian Stakenvicius > <a...@gentoo.org> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> On 09/08/13 01:28 PM, Alexis Ballier wrote: >>> On Fri, 09 Aug 2013 13:14:07 -0400 Ian Stakenvicius >>> <a...@gentoo.org> wrote: >>> >>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>>> >>>> On 09/08/13 01:09 PM, Alexis Ballier wrote: >>>>> On Fri, 09 Aug 2013 18:41:59 +0200 Thomas Sachau >>>>> <to...@gentoo.org> wrote: >>>>>> When when you have done it, try e.g. this: >>>>>> >>>>>> ABI_X86="32" emerge --oneshot =libjpeg-turbo-1.3.0-r2 >>>>> >>>>> >>>>> that's why default abi is in use.force; if this is allowed >>>>> and really disables abi_x86_64 on a stock amd64 profile >>>>> I'd consider this a portage bug. >>>>> >>>> >>>> well, it does -- it's very easy to see just by testing it. >>>> And portage not allowing this doesn't make sense to me >>>> because if it did then we wouldn't have the ability to test >>>> what the build output is going to be for any one particular >>>> ABI_X86 value so I would _really_ hope that this "bug" >>>> doesn't get fixed. >>> >>> I don't get it. We're talking about multi_lib_ not multi arch. >>> There is one ABI you build everything for (what you had before >>> multilib eclasses) and the other ABIs for which you build >>> extra libraries. >>> >> >> I guess I should have done a sed 's/emerge --oneshot (.*)$/ebuild >> install \1/' on that commandline. >> >> My point was, I'd be upset if portage suddenly rejected and >> forced my native_abi value all the time if i'm trying to >> explicitly test a certain build output. > > You're free to mess with your profiles. You're free to override > important variables in make.conf. You're free to break your > system. > > For an example I've seen recently, see e.g. bug #479414 > > How did you test x86 binaries on amd64 before ? With a chroot. This > has not changed. >
I don't want to test the binaries, I want to test the build/install process. But this sub-thread is neither here nor there to the main issue. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlIFMnUACgkQ2ugaI38ACPAxeQEAtLAjadX1VxEfyWJRp6hZToTT ac3P/rLYxS25h80KeHQA/i1ggFCYls9fR/bHnLuu57JICxsV5qeH1oQaJcKS564w =4hiW -----END PGP SIGNATURE-----
