1 |
Frank Peters wrote: |
2 |
> Hello, |
3 |
> |
4 |
> The latest GTK+-2.24.3 failed to build on my system because of the |
5 |
> following error: |
6 |
> |
7 |
> /bin/grep: /usr/lib64/libX11.la: No such file or directory |
8 |
> /bin/sed: can't read /usr/lib64/libX11.la: No such file or directory |
9 |
> libtool: link: `/usr/lib64/libX11.la' is not a valid libtool archive |
10 |
> |
11 |
> The libX11.la that is missing should be in the x11-libs/libX11 package. |
12 |
> But why is libX11.la missing? |
13 |
> |
14 |
> I can emerge libX11 using USE="static-libs" or USE="-static-libs" |
15 |
> but libX11.la is not produced in either case. |
16 |
> |
17 |
> The emerge log when building libX11 always shows the following: |
18 |
> |
19 |
> Removing unnecessary ... x11-libs/libX11-1.4.2/image/usr/lib64/libX11-xcb.la |
20 |
> Removing unnecessary ... x11-libs/libX11-1.4.2/image/usr/lib64/libX11.la |
21 |
> |
22 |
> So the .la files are being produced but are being removed afterwards. |
23 |
> |
24 |
> Does anyone else have a missing /usr/lib64/libX11.la file? |
25 |
> |
26 |
> Frank Peters |
27 |
> |
28 |
> |
29 |
> |
30 |
|
31 |
I think I read on -dev that .la files were being removed. It seems to |
32 |
have been causing trouble when packages were being updating that were |
33 |
linked against each other. So, they made things so that they would work |
34 |
without them and removed them. |
35 |
|
36 |
That is oversimplified since it was a while back but I think that is |
37 |
normal nowadays. Someone correct me if I am wrong on this. |
38 |
|
39 |
Dale |
40 |
|
41 |
:-) :-) |