1 |
i might point out that there is no debug use flag atm. |
2 |
i'm not saying there shouldn't be one, just saying |
3 |
one doesn't currently exist so i dont code for it. |
4 |
as soon as one gets put into use.desc i'll rewrite ebuilds |
5 |
-mike |
6 |
|
7 |
----- Original Message ----- |
8 |
From: "Jon Nelson" <jnelson@×××××××.net> |
9 |
To: "mike" <vapier@×××××××.com> |
10 |
Cc: <gentoo-dev@g.o> |
11 |
Sent: Monday, September 16, 2002 22:22 |
12 |
Subject: Re: [gentoo-dev] --disable-debug, my friend...--disable-debug |
13 |
|
14 |
|
15 |
> On Mon, 16 Sep 2002 21:23:09 -0400 |
16 |
> "mike" <vapier@×××××××.com> wrote: |
17 |
> |
18 |
> > anytime you come across something that doesnt disable debug |
19 |
> > and in fact has the option feel free to post something to the |
20 |
> > list and bugs.gentoo.org ... i usually try to sed out -g and such |
21 |
> > from Makefiles when making ebuild's |
22 |
> |
23 |
> However, that is inappropriate. That is what the debug use flag is for. |
24 |
> I personally feel that the default should be to build with debug symbols |
25 |
> on (but not profiling), but I also believe that for Gentoo (performance |
26 |
> oriented), the best default would be for the 'debug' use flag to be |
27 |
> turned off. In fact, I consider it a bug if an ebuild does *not* allow |
28 |
> for a debug-enabled build to be built. |
29 |
> |
30 |
> |
31 |
> -- |
32 |
> Pound for pound, the amoeba is the most vicious animal on earth. |
33 |
> |
34 |
> Jon Nelson <jnelson@×××××××.net> |
35 |
> C and Python Code Gardener |
36 |
> _______________________________________________ |
37 |
> gentoo-dev mailing list |
38 |
> gentoo-dev@g.o |
39 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
40 |
> |