1 |
2016-07-01 23:42 GMT+08:00 Lei Zhang <zhanglei.april@×××××.com>: |
2 |
> Plan for today: |
3 |
> - write ebuild for NetBSD's crtbegin/end |
4 |
> - write ebuild for libc++abi |
5 |
> |
6 |
> Progress: |
7 |
> - write ebuild for crtbegin/end |
8 |
> |
9 |
> libc++abi's situation is a bit complicated. To configure it, you need |
10 |
> the specify paths to libc++ and LLVM's source. libc++ has a similar |
11 |
> issue: it also needs to know the path to LLVM's source. Actually |
12 |
> libc++'s ebuild maintainer wrote a Makefile to circumvent its cmake |
13 |
> system, which works without knowing LLVM's source path. I guess libc++ |
14 |
> doesn't really need LLVM's source; it's just some quirk of their cmake |
15 |
> system. |
16 |
> |
17 |
> But I can't tell yet if libc++abi really needs libc++ or LLVM's |
18 |
> source. If not, perhaps I can write a Makefile just like libc++'s; |
19 |
> otherwise, maybe I need to keep LLVM's source somewhere after |
20 |
> installing it. |
21 |
|
22 |
It turns out libc++abi doesn't really need LLVM's source, but *does* |
23 |
depend on libc++'s headers. I managed to write a Makefile for it to |
24 |
circumvent cmake, providing libc++'s headers can be found somewhere. |
25 |
|
26 |
The problem is: lib++ is supposed be built after libc++abi. My thought: |
27 |
- if libc++ is already installed (e.g. against libcxxrt), installing |
28 |
libc++abi has no impact on libc++ |
29 |
- otherwise, installing libc++abi also installs libc++, and libc++ |
30 |
will be configured against libc++abi |
31 |
|
32 |
Or alternatively: replace libcxxrt with libc++abi in portage repo, and |
33 |
always install libc++ and libc++abi together, just as clang and LLVM |
34 |
do. |
35 |
|
36 |
Which makes sense more? |
37 |
|
38 |
|
39 |
Lei |