1 |
On Mon, 2020-03-16 at 13:37 +0100, Gerion Entrup wrote: |
2 |
> Am Montag, 16. März 2020, 09:23:49 CET schrieb Michał Górny: |
3 |
> > Hi, |
4 |
> > |
5 |
> > Since 10.0.0 final is around the corner, I'd like to take a minute to |
6 |
> > inform developers of packaging changes in Gentoo that affect its |
7 |
> > revdeps. Following frequently repeated requests from Gentoo developers |
8 |
> > and users, LLVM 10 is stopping to use BUILD_SHARED_LIBS=ON, i.e. split |
9 |
> > shared libraries. Instead, we'll be using the 'dylib' model recommended |
10 |
> > upstream. |
11 |
> > |
12 |
> > This means that sys-devel/{llvm,clang} no longer install those small |
13 |
> > libLLVM*.so and libclang*.so files. Instead, one big libLLVM-${ver}.so |
14 |
> > and libclang-cpp.so.${sover} are installed (yes, I know this historical |
15 |
> > inconsistency sucks). Also note that Clang continues installing |
16 |
> > libclang.so which is a *C* (not C++) library. |
17 |
> > |
18 |
> > Most of LLVM revdeps should not have problem with LLVM dylib, as it was |
19 |
> > the de-facto standard on other distros. llvm-config handles it |
20 |
> > transparently. If you're dealing with a custom build system that |
21 |
> > doesn't handle it, it's as simple as trying '-lLLVM' first (note that |
22 |
> > you will '-L' due to slotting). |
23 |
> > |
24 |
> > Clang revdeps may have trouble with clang-cpp library since it's |
25 |
> > a fairly recent addition. Again, the solution is simple: '-lclang-cpp' |
26 |
> > (repeating: do not confuse it with -lclang which is a different library |
27 |
> > for historical reasons). |
28 |
> > |
29 |
> > sys-devel/lld does not install any libraries anymore. If you ever need |
30 |
> > them, please ping me and we'll try to come up with something upstream. |
31 |
> > |
32 |
> > dev-util/lldb installs liblldb.so. However, I'm not familiar with that |
33 |
> > library and I don't know if it has any consumers. |
34 |
> > |
35 |
> > If you need any help, please don't hesitate to ping me. |
36 |
> |
37 |
> Hi, |
38 |
> |
39 |
> when I compile LLVM for myself, I also always choose SHARED_LIBS simply |
40 |
> because of RAM usage when linking the libraries. In the past, I was not |
41 |
> able to link the single library on my 16 GB machine (I have not tested |
42 |
> it now and this could be dependent on other circumstances). What is the |
43 |
> current expected RAM usage for LLVM 10? |
44 |
> |
45 |
|
46 |
To be honest, I don't know. I have 8G here, and it's entirely |
47 |
sufficient for -j3 build. I don't experience major linking problems |
48 |
as I used to, so things might have improved on binutils end. |
49 |
|
50 |
-- |
51 |
Best regards, |
52 |
Michał Górny |