| 1 |
2016-08-18 21:56 GMT+08:00 C Bergström <cbergstrom@×××××××××.com>: |
| 2 |
> @mgorny may be able to help with some of this and has quite a bit of |
| 3 |
> experience building clang/llvm. Where I work we use a "wrapper" that |
| 4 |
> helps coordinate a lot of the moving pieces. |
| 5 |
> |
| 6 |
> https://github.com/pathscale/llvm-suite/ |
| 7 |
> |
| 8 |
> This may not be the perfect "gentoo" way to handle it, but the |
| 9 |
> approach would produce a clean and correct compiler. With llvm |
| 10 |
> dependencies getting more and more complicated, I'm not sure if it |
| 11 |
> would be possible to have both a gnu-free and also perfect |
| 12 |
> 1-project-source-repo:1-ebuild ratio. |
| 13 |
|
| 14 |
Currently the ebuilds for libunwind, libc++abi and libc++ all involve |
| 15 |
some hackery to support standalone build. And the package clang is |
| 16 |
just a placeholder, while it's actually built in llvm. |
| 17 |
|
| 18 |
Maybe we can put them all into the llvm package, and control what |
| 19 |
components to build via USE flags. |
| 20 |
|
| 21 |
|
| 22 |
Lei |
Archives