Re: [gentoo-user] llvm clang ABI confusion
On 10/02/2016 23:52, James wrote: > Hello, > > My previous post suggest that every file under /etc/portage > > can be parsed for flags and directives. I removed all of the archives > > and that cleanup of /etc/portage/ is in progress. This question > > is unrelated, as best as I can tell. > > > Ok, so I just went to install something and got this :: > > emerge -uDNvtp =dev-java/sbt-0.13.10_rc2 > > [ebuild U ~] dev-java/sbt-0.13.10_rc2::gentoo [0.13.8::gentoo] > > USE="-binary" 210,199 KiB > > [ebuild U ~] dev-lang/scala-2.11.7-r1:2.11/2.11.7::gentoo > > [2.11.4-r1:2.11/2.11.4::gentoo] USE="source -binary -doc -emacs" 0 KiB > > [ebuild U ~] dev-lang/scala-2.10.6:2.10/2.10.6::gentoo > > [2.10.4-r2:2.10/2.10.4::gentoo] USE="source -binary -doc -emacs" 82,629 KiB > > Total: 3 packages (3 upgrades), Size of downloads: 292,827 KiB > > WARNING: One or more updates/rebuilds have been skipped due to a > dependency conflict: > > sys-devel/llvm:0 > > sys-devel/llvm-3.5.0:0/3.5::gentoo, ebuild scheduled for merge > conflicts with > > sys-devel/llvm-3.5.0[clang(-),-debug,python,static- > analyzer,abi_x86_32(-),abi_x86_64(-)] > > required by (sys-devel/clang-3.5.0-r100:0/3.5::gentoo, installed) > > I have both installed:: [I] sys-devel/llvm > > Installed versions: 3.5.0(06:15:37 PM 01/25/2016)(clang libffi ncurses > > python > static-analyzer -debug -doc -gold -libedit -multitarget -ocaml -test -xml > > ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" > > ABI_X86="32 64 -x32" KERNEL="-Darwin -FreeBSD" PYTHON_TARGETS="python2_7 > -pypy" > VIDEO_CARDS="radeon") > > and [I] sys-devel/clang > Installed versions: 3.5.0-r100(12:07:02 PM 01/17/2016)(python > > static-analyzer -debug -multitarget ABI_MIPS="-n32 -n64 -o32" > > ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32") > > > in my /etc/portage/package.use/000.abi I have this > entry:: */* -abi_x86_32 > > > both "egrep -r clang /etc/portage/" and "egrep -r clang /etc/portage/" > return empty. Commenting out the above referenced entry in did not fix the > conflict. > > I still want to ensure I have no 32 bit packages on this system. > Is that my problem that clang/llvm require 32 bit sources? If so, how do I > fix this and keep 32 bit packages off the system? Surely I am confused as to > resolution options. The conflict is very simple. The ebuild says "must have 32 bits!" You said "no zero zip nada 32 bits!' The system says "screw this, you figure it out dude, I give up" Solutions: There are 2, and they are mutually exclusive 1. Relax your stance and accept that some software out there that you might want is 32 bits 2. Refuse to have 32 bits, so give up on llvm and clang. Find something else and move on. You must pick one of those two. There is no magic hidden solution that magically lets you have something and also not have it. -- Alan McKinnon alan.mckin...@gmail.com
[gentoo-user] llvm clang ABI confusion
Hello, My previous post suggest that every file under /etc/portage can be parsed for flags and directives. I removed all of the archives and that cleanup of /etc/portage/ is in progress. This question is unrelated, as best as I can tell. Ok, so I just went to install something and got this :: emerge -uDNvtp =dev-java/sbt-0.13.10_rc2 [ebuild U ~] dev-java/sbt-0.13.10_rc2::gentoo [0.13.8::gentoo] USE="-binary" 210,199 KiB [ebuild U ~] dev-lang/scala-2.11.7-r1:2.11/2.11.7::gentoo [2.11.4-r1:2.11/2.11.4::gentoo] USE="source -binary -doc -emacs" 0 KiB [ebuild U ~] dev-lang/scala-2.10.6:2.10/2.10.6::gentoo [2.10.4-r2:2.10/2.10.4::gentoo] USE="source -binary -doc -emacs" 82,629 KiB Total: 3 packages (3 upgrades), Size of downloads: 292,827 KiB WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict: sys-devel/llvm:0 sys-devel/llvm-3.5.0:0/3.5::gentoo, ebuild scheduled for merge conflicts with sys-devel/llvm-3.5.0[clang(-),-debug,python,static- analyzer,abi_x86_32(-),abi_x86_64(-)] required by (sys-devel/clang-3.5.0-r100:0/3.5::gentoo, installed) I have both installed:: [I] sys-devel/llvm Installed versions: 3.5.0(06:15:37 PM 01/25/2016)(clang libffi ncurses python static-analyzer -debug -doc -gold -libedit -multitarget -ocaml -test -xml ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" KERNEL="-Darwin -FreeBSD" PYTHON_TARGETS="python2_7 -pypy" VIDEO_CARDS="radeon") and [I] sys-devel/clang Installed versions: 3.5.0-r100(12:07:02 PM 01/17/2016)(python static-analyzer -debug -multitarget ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32") in my /etc/portage/package.use/000.abi I have this entry:: */* -abi_x86_32 both "egrep -r clang /etc/portage/" and "egrep -r clang /etc/portage/" return empty. Commenting out the above referenced entry in did not fix the conflict. I still want to ensure I have no 32 bit packages on this system. Is that my problem that clang/llvm require 32 bit sources? If so, how do I fix this and keep 32 bit packages off the system? Surely I am confused as to resolution options. Suggestions? James
Re: [gentoo-user] llvm clang ABI confusion
On Wed, 10 Feb 2016 21:52:16 + (UTC), James wrote: > in my /etc/portage/package.use/000.abi I have this > entry:: */* -abi_x86_32 When package.use (and other package.*) is a directory, the files in it are concatenated, in lexical order. So your entry appears right at the start. This means it can be overridden by any of the other files. > I still want to ensure I have no 32 bit packages on this system. Why? What is special about 32 bit libraries? They are dependencies like any other, if a package needs them why try to stop portage installing them? -- Neil Bothwick Never get into fights with ugly people because they have nothing to lose. pgpR7al99VJE9.pgp Description: OpenPGP digital signature
