Bug 46988

Summary:	Command/flag for emerge to fallback to NO cpu optimisations when building a particular package
Product:	Portage Development	Reporter:	Mark Florian <markrian>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	RESOLVED WONTFIX
Severity:	enhancement
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Mark Florian 2004-04-06 12:04:32 UTC

Instead of having to modify make.conf directly, one should be able to pass a parameter to emerge that disables ALL CPU specific optimisations for the application that is being merged.

e.g.: xine is fairly unstable with my Athlon optimisation settings, but fine without. Other apps are fine with the optimisations. I want to be able to re-emerge xine so that it is built without Athlon specific features, like 3dnow, SSE etc, with something like "emerge --safe-cflags xine-libs", instead of having to manually edit make.conf, emerge xine-libs, and then restore make.conf to how it was.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Actual Results:

Comment 1 Marius Mauch (RETIRED) gentoo-dev

2004-04-06 12:36:58 UTC

what's wrong with
CFLAGS="--your-safe-cflags" emerge xine-libs ?

I'm not for adding this option as it would mean that we have to maintain a list of safe or unsafe CFLAGS in portage and  definitely don't want to check gcc manpages for each release.

Comment 2 Mark Florian 2004-04-06 13:09:25 UTC

That's actually very true. Sorry to have wasted your time! :)

Comment 3 SpanKY gentoo-dev

2004-04-06 14:21:23 UTC

there is already another bug (that i cant find atm) that covers this on a more general scale