| View previous topic :: View next topic |
| Author |
Message |
ManDay
Apprentice
Joined: 22 Jan 2008
Posts: 196
|
 Posted: Tue Jun 19, 2012 6:36 am Post subject: Source code for debug lists - where/how to keep it |
 |
|
I compiled a few packages with debug and nostrip
| Code: | CFLAGS="-O2 -ggdb -pipe"
FEATURES="${FEATURES} nostrip" |
but emerge doesn't keep the source after compilation, so things such as "list" in gdb fail. How should I solve this? Is there a way portage can take care of this and actually keep the source around? |
|
| Back to top |
|
 |
aCOSwt
Advocate
Joined: 19 Oct 2007
Posts: 2075
Location: Between the keyboard and the chair
|
| Posted: Tue Jun 19, 2012 7:39 am Post subject: |
|
|
(Apart from very specific packages) I have no idea if keeping the sources is possible when emerging.
However, you can always : | Code: | | # ebuild $PORTDIR/portage_category/package_name/package_version.ebuild unpack |
Before running gdb.
_________________
In theory there are no differences between theory and practice. In practice, there are.
Don't try to understand my posts. Immanuel Kant never did, he thinks that only music and laughter do not have to mean anything. |
|
| Back to top |
|
|
Hu
Watchman
Joined: 06 Mar 2007
Posts: 7678
|
| Posted: Wed Jun 20, 2012 2:52 am Post subject: |
|
|
| It sounds like you want to install the sources as part of the package. According to man make.conf, this is controlled by the FEATURES value installsources. |
|
| Back to top |
|
|
ManDay
Apprentice
Joined: 22 Jan 2008
Posts: 196
|
| Posted: Wed Jun 20, 2012 6:46 am Post subject: |
|
|
| Thank you, exactly what I needed! |
|
| Back to top |
|
|
|
Portage & Programming
