| 1 |
On Thursday 26 January 2006 11:16, Paul de Vrieze wrote: |
| 2 |
> On Thursday 26 January 2006 16:34, Mikey wrote: |
| 3 |
> > And those instructions have nothing whatsoever to do with common sense |
| 4 |
> > from a new, or even experienced users perspective. Knowing that a gcc |
| 5 |
> > upgrade will break libtool is not common sense, nor is it commonly known. |
| 6 |
> |
| 7 |
> It will not break libtool. |
| 8 |
|
| 9 |
it does and it doesnt |
| 10 |
|
| 11 |
/usr/bin/libtool hardcodes the paths to internal gcc files |
| 12 |
|
| 13 |
normally this isnt an issue as most packages now generate and use their own |
| 14 |
copy of libtool so that they always have the current toolchain information |
| 15 |
|
| 16 |
a few older packages however (jpeg comes to mind) use the system libtool |
| 17 |
instead of bundling their own |
| 18 |
-mike |
| 19 |
-- |
| 20 |
gentoo-dev@g.o mailing list |
Archives