Summary: | sys-libs/glibc-2.37-r3[vanilla] fails to compile because of sandbox violation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | CONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
sandbox.log emerge --info |
Description
Agostino Sarubbo
![]() Please do provide the full log (build.log + sandbox.log). and emerge --info. I can't easily check right now and it's unclear to me which phase this is happening in. (In particular, the sandbox version might matter here too.) Created attachment 865184 [details]
build.log
Created attachment 865185 [details]
sandbox.log
Created attachment 865186 [details]
emerge --info
https://gitweb.gentoo.org/proj/toolchain/glibc-patches.git/tree/9999/0001-Disable-ldconfig-during-install.patch On the one hand, USE=vanilla is doing exactly what you wanted, but perhaps a bit too literally. The patch should probably be included despite USE=vanilla. (In reply to Sam James from comment #6) > https://gitweb.gentoo.org/proj/toolchain/glibc-patches.git/tree/9999/0001- > Disable-ldconfig-during-install.patch > > On the one hand, USE=vanilla is doing exactly what you wanted, but perhaps a > bit too literally. The patch should probably be included despite USE=vanilla. I agree |