| 1 |
On Saturday, 12 March 2022 08:43:02 GMT Dale wrote: |
| 2 |
> Michael wrote: |
| 3 |
> > On Saturday, 12 March 2022 01:34:45 GMT Dale wrote: |
| 4 |
> >> Howdy, |
| 5 |
> >> |
| 6 |
> >> I just noticed this in my updates: |
| 7 |
> >> |
| 8 |
> >> [ebuild U ] sys-devel/llvm-13.0.1:13::gentoo [13.0.0:13::gentoo] |
| 9 |
> >> USE="binutils-plugin%* libffi ncurses xml -debug -doc -exegesis -libedit |
| 10 |
> >> -test -xar -z3 (-gold%*)" ABI_X86="32 (64) (-x32)" |
| 11 |
> >> LLVM_TARGETS="(AArch64*) (AMDGPU) (ARM*) (AVR*) (BPF) (Hexagon*) |
| 12 |
> >> (Lanai*) (MSP430*) (Mips*) (NVPTX) (PowerPC*) (RISCV*) (Sparc*) |
| 13 |
> >> (SystemZ*) (WebAssembly*) (X86) (XCore*) (-ARC) (-CSKY) (-M68k) (-VE)" |
| 14 |
> >> |
| 15 |
> >> The LLVM_TARGETS= part looks odd. Why do I need ARM, PowerPC, Sparc etc |
| 16 |
> >> here? Is that correct? The old still installed version doesn't have |
| 17 |
> >> those enabled. |
| 18 |
> >> |
| 19 |
> >> Thanks. |
| 20 |
> >> |
| 21 |
> >> Dale |
| 22 |
> >> |
| 23 |
> >> :-) :-) |
| 24 |
> > |
| 25 |
> > You don't need any of these targets in llvm and clang any more than I do. |
| 26 |
> > There's a bug which explains why these arch targets are now being forced, |
| 27 |
> > but I can't find it. |
| 28 |
> |
| 29 |
> That was my thinking when I saw it. It just looked odd to me. I found |
| 30 |
> this bug. |
| 31 |
> |
| 32 |
> https://bugs.gentoo.org/767700 |
| 33 |
> |
| 34 |
> Is that the one? It mentions the target but I don't quite understand |
| 35 |
> the why. The biggest thing, will this break something if I let it do |
| 36 |
> it? I don't have any settings of my own on this package. It was done |
| 37 |
> by a dev, who I assume has a good reason for this. |
| 38 |
> |
| 39 |
> Dale |
| 40 |
> |
| 41 |
> :-) :-) |
| 42 |
|
| 43 |
That's the one, yes. As I understand it unless all these targets are set sys- |
| 44 |
devel/lld breaks. |
Archives