1 |
This is mostly a nit-like RFC. The developer profile adds a |
2 |
profile.bashrc, which prints the "You should enable -g (or higher) for |
3 |
debugging!" message when "-g" is not in CFLAGS. |
4 |
|
5 |
I wonder if we can remove that file. It has been added 3 years ago: |
6 |
|
7 |
<http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/targets/developer/profile.bashrc?view=markup> |
8 |
|
9 |
It is not obvious from looking at emerge output what prints this |
10 |
message, it doesn't fit well with the rest of the output, and may be |
11 |
easy to miss: |
12 |
|
13 |
* USE: elibc_glibc gtk kernel_linux test userland_GNU x86 |
14 |
* FEATURES: sandbox splitdebug test userpriv usersandbox |
15 |
You should enable -g (or higher) for debugging! |
16 |
>>> Unpacking source... |
17 |
>>> Unpacking mtr-0.80.tar.gz to /var/tmp/portage/net-analyzer/mtr-0.80/work |
18 |
|
19 |
I think it is not necessary for every developer to add "-g" to CFLAGS - |
20 |
the main point is to have any symbols at all, not just |
21 |
to-the-file-and-line-precise debugging info. If the latter is needed, |
22 |
the developer will obviously know what to do. |
23 |
|
24 |
What do you think about removing |
25 |
gentoo-x86/profiles/targets/developer/profile.bashrc file? |