1 |
On 10/02/2016 23:52, James wrote: |
2 |
> Hello, |
3 |
> |
4 |
> My previous post suggest that every file under /etc/portage |
5 |
> |
6 |
> can be parsed for flags and directives. I removed all of the archives |
7 |
> |
8 |
> and that cleanup of /etc/portage/ is in progress. This question |
9 |
> |
10 |
> is unrelated, as best as I can tell. |
11 |
> |
12 |
> |
13 |
> Ok, so I just went to install something and got this :: |
14 |
> |
15 |
> emerge -uDNvtp =dev-java/sbt-0.13.10_rc2 |
16 |
> |
17 |
> [ebuild U ~] dev-java/sbt-0.13.10_rc2::gentoo [0.13.8::gentoo] |
18 |
> |
19 |
> USE="-binary" 210,199 KiB |
20 |
> |
21 |
> [ebuild U ~] dev-lang/scala-2.11.7-r1:2.11/2.11.7::gentoo |
22 |
> |
23 |
> [2.11.4-r1:2.11/2.11.4::gentoo] USE="source -binary -doc -emacs" 0 KiB |
24 |
> |
25 |
> [ebuild U ~] dev-lang/scala-2.10.6:2.10/2.10.6::gentoo |
26 |
> |
27 |
> [2.10.4-r2:2.10/2.10.4::gentoo] USE="source -binary -doc -emacs" 82,629 KiB |
28 |
> |
29 |
> Total: 3 packages (3 upgrades), Size of downloads: 292,827 KiB |
30 |
> |
31 |
> WARNING: One or more updates/rebuilds have been skipped due to a |
32 |
> dependency conflict: |
33 |
> |
34 |
> sys-devel/llvm:0 |
35 |
> |
36 |
> sys-devel/llvm-3.5.0:0/3.5::gentoo, ebuild scheduled for merge |
37 |
> conflicts with |
38 |
> |
39 |
> sys-devel/llvm-3.5.0[clang(-),-debug,python,static- |
40 |
> analyzer,abi_x86_32(-),abi_x86_64(-)] |
41 |
> |
42 |
> required by (sys-devel/clang-3.5.0-r100:0/3.5::gentoo, installed) |
43 |
> |
44 |
> I have both installed:: [I] sys-devel/llvm |
45 |
> |
46 |
> Installed versions: 3.5.0(06:15:37 PM 01/25/2016)(clang libffi ncurses |
47 |
> |
48 |
> python |
49 |
> static-analyzer -debug -doc -gold -libedit -multitarget -ocaml -test -xml |
50 |
> |
51 |
> ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" |
52 |
> |
53 |
> ABI_X86="32 64 -x32" KERNEL="-Darwin -FreeBSD" PYTHON_TARGETS="python2_7 -pypy" |
54 |
> VIDEO_CARDS="radeon") |
55 |
> |
56 |
> and [I] sys-devel/clang |
57 |
> Installed versions: 3.5.0-r100(12:07:02 PM 01/17/2016)(python |
58 |
> |
59 |
> static-analyzer -debug -multitarget ABI_MIPS="-n32 -n64 -o32" |
60 |
> |
61 |
> ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32") |
62 |
> |
63 |
> |
64 |
> in my /etc/portage/package.use/000.abi I have this |
65 |
> entry:: */* -abi_x86_32 |
66 |
> |
67 |
> |
68 |
> both "egrep -r clang /etc/portage/" and "egrep -r clang /etc/portage/" |
69 |
> return empty. Commenting out the above referenced entry in did not fix the |
70 |
> conflict. |
71 |
> |
72 |
> I still want to ensure I have no 32 bit packages on this system. |
73 |
> Is that my problem that clang/llvm require 32 bit sources? If so, how do I |
74 |
> fix this and keep 32 bit packages off the system? Surely I am confused as to |
75 |
> resolution options. |
76 |
|
77 |
The conflict is very simple. |
78 |
|
79 |
The ebuild says "must have 32 bits!" |
80 |
You said "no zero zip nada 32 bits!' |
81 |
The system says "screw this, you figure it out dude, I give up" |
82 |
|
83 |
Solutions: There are 2, and they are mutually exclusive |
84 |
|
85 |
1. Relax your stance and accept that some software out there that you |
86 |
might want is 32 bits |
87 |
2. Refuse to have 32 bits, so give up on llvm and clang. Find something |
88 |
else and move on. |
89 |
|
90 |
You must pick one of those two. There is no magic hidden solution that |
91 |
magically lets you have something and also not have it. |
92 |
|
93 |
|
94 |
|
95 |
-- |
96 |
Alan McKinnon |
97 |
alan.mckinnon@×××××.com |