Summary: | sys-apps/sandbox-2.11: all execvpe calls get denied | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo's Haskell Language team <haskell> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alunduil, root, sandbox, uzytkownik2 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-haskell:entropy-0.3.7:20160329-140132.log
emerge-history.txt environment sandbox-27008.log |
Description
Toralf Förster
2016-03-29 14:06:21 UTC
Created attachment 429226 [details]
dev-haskell:entropy-0.3.7:20160329-140132.log
Created attachment 429228 [details]
emerge-history.txt
Created attachment 429230 [details]
environment
Created attachment 429232 [details]
sandbox-27008.log
Alex also found similar issue on other haskell packages. I wonder what changed recently. [32;01m*[0m Using cabal-1.22.6.0. [32;01m*[0m Prepending /usr/lib64/ghc-7.10.2 to LD_LIBRARY_PATH /usr/bin/ghc -package Cabal-1.22.6.0 --make /var/tmp/paludis/dev-haskell-hlint-1.9.32/work/hlint-1.9.32/Setup.hs -threaded -dynamic -o setup [1 of 1] Compiling Main ( /var/tmp/paludis/dev-haskell-hlint-1.9.32/work/hlint-1.9.32/Setup.hs, /var/tmp/paludis/dev-haskell-hlint-1.9.32/work/hlint-1.9.32/Setup.o ) [31;01m*[0m [31;01mACCESS DENIED[0m: execvpe: /usr/bin/x86_64-pc-linux-gnu-gcc <no location info>: Warning: Couldn't figure out C compiler information! Make sure you're using GNU gcc, or clang Linking setup ... [31;01m*[0m [31;01mACCESS DENIED[0m: execvpe: /usr/bin/x86_64-pc-linux-gnu-gcc <no location info>: Warning: Couldn't figure out linker information! Make sure you're using GNU ld, GNU gold or the built in OS X linker, etc. + sandbox@ : Does this denial make sense for you? Looks like execvpe() is a glibc-2.21+ function. ghc used to call execve() on older libc. git.haskell.org/packages/unix.git/blob/HEAD:/cbits/execvpe.c#l71 [speculation] ghc built against new glibc gets these denials. rebuilding ghc locally against glibc-2.22-r2 to verify. > [speculation] ghc built against new glibc gets these denials. rebuilding ghc
> locally against glibc-2.22-r2 to verify.
This failed. I don't get denials with rebuilt ghc-7.10.3/glibc-2.22-r2/gcc-5.3.0/sys-apps/sandbox.
I am getting these errors trying to emerge ANYTHING since yesterday. How can I update my system now because updating sandbox also fails? should be fixed w/sandbox-2.11-r2 https://gitweb.gentoo.org/proj/sandbox.git/commit/?id=31a135d261a9bc1d65b1fa484345a858bab84db8 How can I update to -r2 from the affected sys-apps/sandbox-2.11? This seems a serious issue here. sandbox-2.11-r2 doesn't fix this It is possible to revert to sandbox-2.10-r2 by emerging with FEATURES="-sandbox -usersandbox" (In reply to davech from comment #12) I'm just curious if this could be automated in a scenario were all users would be affected ? (In reply to Toralf Förster from comment #13) it cannot. welcome to ~arch. *** Bug 578884 has been marked as a duplicate of this bug. *** |