xarchiveshash:fd4cc9c19b9ef548fbf54fa6d3f6f5d0

* Re: [gentoo-dev] new ebuild variables proposal...
  @ 2002-04-05 18:45 99% ` George Shapovalov
  0 siblings, 0 replies; 1+ results
From: George Shapovalov @ 2002-04-05 18:45 UTC (permalink / raw
  To: gentoo-dev

This is in fact possible and does not require new flag introguction. Just
define you CFLAGS in src_compile and pass them to make. You can easily to
redefine or add something to C[XX]Flags. If you want to only remove some
specific flags you will need to do some bash magic (though I am sure such
utils exist already, if not its a few lines of python code).
In the last case you indeed may want some automation on the side of
portage scripts. For details on how to do such CFLAGS modifications
just grep for CFLAGS under /usr/portage and read files which match.

If you want this to be seriously considered by core developers (since
this is a modification to portage) this is what you will need to do (from
my experience):
write more detailed proposal (not very long though) and spend some time on
motivations - why this is necessary. Then submit this onto bugs.gentoo.org
as a feature request (put it under: gentoo/portage/enhancement).

George

On Fri, 5 Apr 2002, Zach Forrest wrote:

> I've been working on an ebuild recently and the package won't compile
> with the '-funroll-loops' compiler flag. It might be nice to have a
> couple of variables such as 'BAD_CFLAGS' and 'BAD_CXXFLAGS' that would
> tell portage to remove these compiler flags for a particular ebuild.
> This would provide a uniform way to deal with any similar problems
> without someone having to modify their optimization settings for one ebuild.
>
> Any thoughts?
>
> Zach
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>

^ permalink raw reply	[relevance 99%]