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