Created attachment 493404 [details] emerge --info I'm getting this access violation error upon sys-libs/glibc-2.25-r4 emerge. It was, at first, complaining about sys-libs/timezone-data-2017b, as being a blocker. >>> Completed installing glibc-2.25-r4 into /var/tmp/portage/sys-libs/glibc-2.25-r4/image/ * Final size of build directory: 588440 KiB * Final size of installed tree: 69820 KiB * --------------------------- ACCESS VIOLATION SUMMARY -------------------- ------- * LOG FILE: "/var/log/sandbox/sandbox-32269.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: open_wr S: deny P: /etc/ld.so.cache~ A: /etc/ld.so.cache~ R: /etc/ld.so.cache~ C: /var/tmp/portage/sys-libs/glibc-2.25-r4/work/build-x86-x86_64-pc-linux- gnu-nptl/elf/ldconfig -r /var/tmp/portage/sys-libs/glibc-2.25-r4/image /lib32 /usr/lib32 F: open_wr S: deny P: /etc/ld.so.cache~ A: /etc/ld.so.cache~ R: /etc/ld.so.cache~ C: /var/tmp/portage/sys-libs/glibc-2.25-r4/work/build-amd64-x86_64-pc-linux- gnu-nptl/elf/ldconfig -r /var/tmp/portage/sys-libs/glibc-2.25-r4/image /lib64 /usr/lib64 * ------------------------------------------------------------------------- -------
Without the "vanilla" flag, it merges perfectly.
This works as intended. vanilla gcc runs ldconfig explicitly. You would ether need to: - disable sandbox when glibc is installed into staging directory(FEATURES=-sandbox) - apply a patch through /etc/portage/patches/: https://github.com/gentoo/glibc/commit/1eff1226630034286c3ae5fa1376eb76211690df Why do you need USE=vanilla?
(In reply to Sergei Trofimovich from comment #2) > This works as intended. vanilla gcc runs ldconfig explicitly. > You would ether need to: > - disable sandbox when glibc is installed into staging > directory(FEATURES=-sandbox) > - apply a patch through /etc/portage/patches/: > https://github.com/gentoo/glibc/commit/ > 1eff1226630034286c3ae5fa1376eb76211690df > > Why do you need USE=vanilla? I don't. The flag was lingering behind, because on a previous version of glibc it would only build if the vanilla was enabled, if I remember right. I have already updated it, without the vanilla flag and moved on so, as far as I'm concerned, this bug can be closed. But I think that, if the behavior is intended and this will happen every time, then it could have flag restrictions as to say that if the vanilla flag is enabled, than the sandbox feature needs to be disabled. Just and idea...
(In reply to Frederico Freire Boaventura from comment #3) > (In reply to Sergei Trofimovich from comment #2) > > This works as intended. vanilla gcc runs ldconfig explicitly. > > You would ether need to: > > - disable sandbox when glibc is installed into staging > > directory(FEATURES=-sandbox) > > - apply a patch through /etc/portage/patches/: > > https://github.com/gentoo/glibc/commit/ > > 1eff1226630034286c3ae5fa1376eb76211690df > > > > Why do you need USE=vanilla? > > I don't. The flag was lingering behind, because on a previous version of > glibc it would only build if the vanilla was enabled, if I remember right. > > I have already updated it, without the vanilla flag and moved on so, as far > as I'm concerned, this bug can be closed. > > But I think that, if the behavior is intended and this will happen every > time, then it could have flag restrictions as to say that if the vanilla > flag is enabled, than the sandbox feature needs to be disabled. Just and > idea... Aaand that's a good reason why USE=vanilla *here* is not such a great idea. # Andreas K. Huettel <dilfridge@gentoo.org> (9 Sep 2017) # Potentially destructive. Use it only if you know what you're doing. sys-libs/glibc vanilla commit 9f15d427745001a5ad0928cb78cc7fd4a017ed1b (HEAD -> master, origin/master, origin/HEAD) Author: Andreas K. Hüttel <dilfridge@gentoo.org> Date: Sat Sep 9 21:22:28 2017 +0200 profiles: Mask vanilla use flag for sys-libs/glibc profiles/base/package.use.mask | 4 ++++ 1 file changed, 4 insertions(+)
