| 1 |
Others have already coverd the major points, so just a couple of |
| 2 |
things to add... |
| 3 |
|
| 4 |
On 6/8/06, Bob Young <BYoung@××××××××××.com> wrote: |
| 5 |
> Are you absolutely 100% sure that every single system utility and |
| 6 |
> application is *dynamically* linked, and that no apps or utilities anywhere |
| 7 |
> in the system specifies *static* linking? |
| 8 |
|
| 9 |
I didn't say "every single system utility and application". I said |
| 10 |
"basically every program", which was a bad way of saying "almost all", |
| 11 |
since it might not be obvious for non-native english speakers (and |
| 12 |
even some native english speakers). |
| 13 |
|
| 14 |
> > There are a few statically linked programs that will include glibc |
| 15 |
> > internally. These are used only for system recovery purposes...there |
| 16 |
> > is no need to worry about them at all. |
| 17 |
> |
| 18 |
> Really, so people who intentionally and specifically want to upgrade |
| 19 |
> absolutely *everything* should not worry about what gets left out because |
| 20 |
> Richard says it's unimportant? |
| 21 |
|
| 22 |
No. They should follow the gcc upgrade guide that says emerge -e |
| 23 |
system followed by emerge -e world. |
| 24 |
|
| 25 |
BTW, I was incorrect when I stated "only for system recover purposes". |
| 26 |
The static programs do include things like busybox (which doesn't use |
| 27 |
glibc at all AFAIK), nash, and insmod.static, which are /mostly/ |
| 28 |
useful for system recovery. But it also includes things that have to |
| 29 |
run before the root filesystem is mounted, like splash and suspend |
| 30 |
utilities. |
| 31 |
|
| 32 |
I still think anybody worried about the performance of (e.g.) lvm is a |
| 33 |
bit crazy, but if they want to remerge it after remerging glibc to get |
| 34 |
the new "optimized" code, well, so be it... |
| 35 |
|
| 36 |
> The same holds true for libstdc++-v3 orginally it was built with the default |
| 37 |
> system compiler, it makes sense to have it rebuilt with the new compiler. |
| 38 |
|
| 39 |
There is simply no way to build libstdc++-v3 with the new compiler; it |
| 40 |
would break any programs that need it. Gcc likes to make incompatible |
| 41 |
changes in the C++ ABI from one version to the next, so building -v3 |
| 42 |
with the new gcc would give you the old stdc++ library, but the new |
| 43 |
ABI, and your programs would be broken. |
| 44 |
|
| 45 |
This is one of the major reasons that gcc uses itself to build itself, |
| 46 |
to make sure that it's ABI is consistent. |
| 47 |
|
| 48 |
-Richard |
| 49 |
-- |
| 50 |
gentoo-user@g.o mailing list |
Archives