| 1 |
On May 14, 2007, at 15:49 , Fabian Groffen wrote: |
| 2 |
|
| 3 |
> On 14-05-2007 15:40:51 +0200, Johan Hattne wrote: |
| 4 |
> |
| 5 |
>> Then, I don't quite see the principal problem with configuring to / |
| 6 |
>> usr/lib, |
| 7 |
>> moving lib{,n}curses{,w} (plus some $(get_libname) trickery) to / |
| 8 |
>> lib and |
| 9 |
>> gen_usr_ldscript() the moved libraries. Since gen_usr_ldscript() |
| 10 |
>> creates |
| 11 |
>> symlinks or wrappers in /usr/lib and not /lib, above seems easier |
| 12 |
>> to me |
| 13 |
>> than doing it the other way around? |
| 14 |
> |
| 15 |
> Because all libs are moved to lib, and only the .a remains in usr/lib, |
| 16 |
> to make sure GCC doesn't do static linking, a symlink of the libs is |
| 17 |
> placed in usr/lib next to the static lib (.a). So the real |
| 18 |
> location of |
| 19 |
> the libs is in /lib. |
| 20 |
|
| 21 |
No, as far as I can see, only libcurses.*.dylib (and if unicode is in |
| 22 |
use, libcursesw.*.dylib) are moved to /lib. lib{form,menu,panel} and |
| 23 |
their wide versions are put into /usr/lib, and those are the ones |
| 24 |
that cause problems, because there are no links from /lib to /usr/ |
| 25 |
lib. gen_usr_ldscript() doesn't create links from /lib to /usr/lib. |
| 26 |
|
| 27 |
// Cheers; Johan |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-alt@g.o mailing list |
Archives