Ciaran McCreesh wrote:
Well, you're assuming that a) everyone's using a C compiler, b) that
gcc has the slightest clue what it's doing, c) that the user has no
problem using nasty hacks to regain control, d) that this information
is only needed at compile time, e) that various gcc internal
definitions won't change... You're adding a lot of complexity, and thus
room for very weird breakages, to something that doesn't need it.
as for...
b) You kind of have to assume that when running a system that was
compiled from ground up with gcc
c) This is not about "regaining" control. Currently, users who want to
cross-compile are screwed and need nasty use.mask-hacks to not end up
with broken binaries. The inability to provide per-package CFLAGS is a
missing feature in portage, it's got nothing to do with this issue.
--
Kind Regards,
Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list
