| View previous topic :: View next topic |
| Author |
Message |
maverickmage
n00b
Joined: 27 Nov 2004
Posts: 60
|
 Posted: Sat Oct 15, 2005 6:48 pm Post subject: If I recompile, do I have to re-emerge everything again? |
 |
|
Sorry for the newbie question...
But what the title says... |
|
| Back to top |
|
 |
widremann
Veteran
Joined: 14 Mar 2005
Posts: 1314
|
| Posted: Sat Oct 15, 2005 6:53 pm Post subject: |
|
|
| No. |
|
| Back to top |
|
|
maverickmage
n00b
Joined: 27 Nov 2004
Posts: 60
|
| Posted: Sat Oct 15, 2005 6:54 pm Post subject: |
|
|
| thanks |
|
| Back to top |
|
|
JSharku
Apprentice
Joined: 09 Feb 2003
Posts: 189
Location: Belgium
|
| Posted: Sun Oct 16, 2005 12:03 am Post subject: |
|
|
You shouldn't recompile everything no, but if you have done some major updates like glibc you should run revdep-rebuild which will determine what packages need to be recompiled, if any. See also 'man revdep-rebuild'.
Sharku
_________________
If only life were portage-driven: | Code: | | USE="-bitch -in-laws nice gorgeous smart" emerge girlfriend |
*sigh*
--
Open Source for Windows! |
|
| Back to top |
|
|
extraketchup
n00b
Joined: 21 Jun 2004
Posts: 29
Location: Maine
|
| Posted: Sun Oct 16, 2005 12:50 pm Post subject: glibc |
|
|
| Quote: | | You shouldn't recompile everything no, but if you have done some major updates like glibc you should run revdep-rebuild which will determine what packages need to be recompiled, if any. |
Quick question about glibc (this may sound noobish) - would a package need recompiled if they dynamically link to glibc? I thought you would only need to recompile if using static links.
EK
_________________
There are more things in heaven and earth, Horatio, Than are dreamt of in your philosophy. |
|
| Back to top |
|
|
JSharku
Apprentice
Joined: 09 Feb 2003
Posts: 189
Location: Belgium
|
| Posted: Sun Oct 16, 2005 1:20 pm Post subject: |
|
|
It's the other way round. If you statically link to glibc it means that those portions of glibc (or any other lib it links to) that your program uses get compiled into its own binary. If you change glibc afterwards you still have the "original" portions inside your binary.
On the other hand if you use dynamic linking, there will be pointers to certain lib functions in the program, but the code to execute these functions is kept in the library. Now if you change your library, these functions might be moved around or modified or deleted or... so in that case the pointers to these functions need to be updated as well to reflect those changes. Mind you, it's not always necessary to recompile your program just because you updated a library, but that's why there's revdep-rebuild to find out if it's necessary.
Sharku
_________________
If only life were portage-driven: | Code: | | USE="-bitch -in-laws nice gorgeous smart" emerge girlfriend |
*sigh*
--
Open Source for Windows! |
|
| Back to top |
|
|
|
Kernel & Hardware
