1 |
Most ebuilds for packages that are picky about optimization settings, set |
2 |
their own CFLAGS & CXXFLAGS. If you will post what package you tried to |
3 |
compile and could not due to a CFLAGS setting, it would help us. |
4 |
|
5 |
For example, if you look at the glibc ebuild you will find that CFLAGS is |
6 |
set to -O2 instead of the possible default of -O3, because linuxthreads |
7 |
which is part of glibc won't compile with -O3 apparently. |
8 |
|
9 |
Personally, I feel this is the right way to handle this. Otherwise, just |
10 |
having a BAD_CFLAGS variable takes away optimizations from programs which |
11 |
might have a problem with 1 but not all optimization flags. |
12 |
|
13 |
-Jared H. |
14 |
|
15 |
On Fri, 5 Apr 2002, Zach Forrest wrote: |
16 |
|
17 |
> I've been working on an ebuild recently and the package won't compile |
18 |
> with the '-funroll-loops' compiler flag. It might be nice to have a |
19 |
> couple of variables such as 'BAD_CFLAGS' and 'BAD_CXXFLAGS' that would |
20 |
> tell portage to remove these compiler flags for a particular ebuild. |
21 |
> This would provide a uniform way to deal with any similar problems |
22 |
> without someone having to modify their optimization settings for one ebuild. |
23 |
> |
24 |
> Any thoughts? |
25 |
> |
26 |
> Zach |
27 |
> |
28 |
> _______________________________________________ |
29 |
> gentoo-dev mailing list |
30 |
> gentoo-dev@g.o |
31 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
32 |
> |
33 |
|
34 |
-- |
35 |
Using the internet as it was originally intended... |
36 |
for the further research of pornography and pipebombs. |