Bug 86923 – Portage sandbox compiled with minimal CFLAGS

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Kaiting Chen 2005-03-27 19:58:08 UTC]

The portage ebuild compiles the sandbox with really low CFLAGS. It should just use the regular ones in make.conf.

Reproducible: Always
Steps to Reproduce:

[Comment 1 Seemant Kulleen (RETIRED) 2005-03-28 07:22:20 UTC]

possibly because the sandbox developers (az and the portage team) know better than to trust user CFLAGS for something as critical as the sandbox?  Just a guess.

[Comment 2 Kaiting Chen 2005-03-28 10:11:09 UTC]

I thought of something like that, but if you're going to set crazy CFLAGS, you might as well be aware of the consequences. I don't know how much really low CFLAGS are going to slow down portage; my guess is not much, considering the sandbox is only used for a little part of the emerge process, but I'm really looking for ways to optimize, and I think that compiling the sandbox without user CFLAGS is pretty unnecessary.

[Comment 3 Kaiting Chen 2005-03-28 10:12:09 UTC]

And the sandbox isn't all THAT critical. How many ebuilds really violate the sandbox? The only time its critical at all is if a user is screwing around with an overlay.

[Comment 4 Ciaran McCreesh 2005-03-28 11:39:43 UTC]

Except that if your sandbox lib is broken, you can't compile anything...

[Comment 5 Brian Harring (RETIRED) 2005-03-28 17:39:04 UTC]

if the sandbox segfaults, it'll pretty much take out any and all processess running sandbox'd.
Meanwhile, marking this later.  the autotooling of sandbox allows for it, although the question of filtering/limiting cflags hasn't been addressed.

[Comment 6 Marius Mauch (RETIRED) 2007-01-11 14:47:13 UTC]

Reopening for reassignment

[Comment 7 SpanKY 2007-01-11 16:50:34 UTC]

this has already been addressed