On 04/01/2014 01:54 AM, Michał Górny wrote:
>Also, I don't see that it should be an issue, but do you think this
>might affect catalyst runs --- I have to ask because
>repairing/reconfiguring seeds is a lot of work.
Well, I think this mostly depends on whether you want multiple multilib
ABIs in stages -- or if you assume that the toolchain is enough,
and people will build other ABIs as they need.
Though I think that once toolchain switches to abi_* flags (vapier
seems to show interest in that), we will use.force the necessary ABIs
on it and its dependencies, so there should be no explicit need for
change.
However, I guess the toolchain changes will be sent out for testing
anyway, so releng can check first hand.
I have taken a non-standard approach to the hardened/linux/uclibc
profiles where I do no inherit from arch. There was too much cruft in
arch, so I just mirror the relevant stuff including the abi flag stuff.
I understand my approach has pros/cons ... but give out the should when
the change is being tested and I'll see if I'm about to have any
breakage. I currently seed at least 12 different
arches/isa/abi/hard-soft float combinations which would be a pita to fix
manually on native (read slow) hardware.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : [email protected]
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
