Summary: | sys-libs/glibc-2.6.1: libsandbox: Can't resolve fopen: (null) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Markus <M4rkusXXL> |
Component: | Sandbox | Assignee: | Sandbox Maintainers <sandbox> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | andreas, caluml, flammie, kryptonite418787, leio, mike, miksir, tc, vroman, xiaomhome |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Markus
2007-12-19 10:56:11 UTC
I can confirm this. Bug strangely I emerged glibc without any problems (during emerge -uDavN system). Afterwards libsandbox began to complain and I found similar errors: >>> Compiling source in /var/tmp/portage/sys-fs/udev-115-r1/work/udev-115 ... /usr/bin/x86_64-pc-linux-gnu-ar GENHDR udev_version.h CC udev_device.o CC udev_config.o CC udev_node.o CC udev_db.o CC udev_sysfs.o libsandbox: Can't resolve access: (null) make: *** [udev_sysfs.o] Error 1 * * ERROR: sys-fs/udev-115-r1 failed. * Call stack: * ebuild.sh, line 1701: Called dyn_compile * ebuild.sh, line 1039: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * udev-115-r1.ebuild, line 126: Called die * The specific snippet of code: * emake \ * EXTRAS="${extras}" \ * libudevdir=${udev_helper_dir} \ * CROSS_COMPILE=${mycross} \ * OPTFLAGS="" \ * ${myconf} || die * The die message: * (no error message) Most notably the 'Can't resolve <something>' came randomly. I'm quite sure I'm not a victim of hardware malfunction as everything emerged fine with FEATURES="-sandbox" emerge ... # emerge --info Portage 2.1.3.19 (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.23-gentoo-r3 x86_64) ================================================================= System uname: 2.6.23-gentoo-r3 x86_64 Intel(R) Xeon(R) CPU E5335 @ 2.00GHz Timestamp of tree: Mon, 17 Dec 2007 01:47:01 +0000 ccache version 2.4 [disabled] app-shells/bash: 3.2_p17 dev-lang/python: 2.4.4-r6 dev-python/pycrypto: 2.0.1-r6 dev-util/ccache: 2.4-r7 sys-apps/baselayout: 1.12.9-r2 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.61-r1 sys-devel/automake: 1.9.6-r2, 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.22-r2 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer sandbox sfperms strict unmerge-orphans userfetch" GENTOO_MIRRORS="ftp://ftp.gentoo.diku.dk/ http://mirror.uni-c.dk/pub/gentoo/" LINGUAS="fr en de it sv da en_GB" MAKEOPTS="-j9" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.diku.dk/gentoo-portage/" USE="acl amd64 berkdb bitmap-fonts cjk cli cracklib crypt cups dri fortran gdbm gpm iconv ipv6 isdnlog ldap logrotate maildir mbox midi mmx mudflap ncurses nls nptl nptlonly openmp pam pcre perl pppd python readline reflection sasl session slang spl sse sse2 ssl tcpd truetype-fonts type1-fonts unicode x86 xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="fr en de it sv da en_GB" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i810 mach64 mga neomagic nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY *** Bug 202842 has been marked as a duplicate of this bug. *** Got the same trouble today on new kernel. Except usual i turn two new options in kernel: -fstack-protector and SLUB allocator. After rollback this options (fstack disabled, SLAB allocator) glibc was compiled without any troubles. Please, all, review your kernel config about this options. I had the same type of problems (different packages failed though) on my newly installed nocona based system, which seemed to be solved by re-emerging sandbox with FEATURE sandbox turned off (as stated in the elog when emerging sandbox). In other words: FEATURES="-sandbox" emerge -av1 sandbox did the trick for me. Is that helpful to resolve this? I tried both, but they do not work for me. My current kernel-config tells me: # CONFIG_CC_STACKPROTECTOR is not set # CONFIG_SLUB is not set And FEATURES="-sandbox -usersandbox" emerge -1av sandbox emerge -1av glibc didnt worked. But FEATURES="-sandbox -usersandbox" emerge -1av glibc obviously worked. I ran into the same problem, but I resolved it from this forum thread -> http://forums.gentoo.org/viewtopic-p-4698824.html?sid=075a4638579cf257cf7713e5cc16db74 I installed a fresh stage3 on my new laptop (Intel Core 2 Duo, 2.2GHz). Once I got through the install process, I did "emerge -vuDNe world". It failed twice at glibc-2.6.1 with the same error message: libsandbox: Can't resolve fopen: (null) All I had to do was: emerge --oneshot sandbox And glibc was able to compile just fine I saw this same error too on a very fresh install that has emerge -e system for stage2 going right now. One thing that went wrong earlier was glibc not getting recompiled in stage1 due to power issue and moving on, but sandbox was done before glibc in stage1 anyhow, I believe I ran across this as well. Rebuilding/rebooting the kernel did help, but only once I downgraded to 2.6.22. With 2.6.23 I was unable to build glibc-2.6.1. if it fails for sandbox-1.3+ and glibc-2.8+, we can take a look ive rewritten the code in question because of the stuff changed for Bug 206678 to handle things dynamically at runtime older versions "just work" because RTLD_NEXT was changed to never actually be used http://git.overlays.gentoo.org/gitweb/?p=proj/sandbox.git;a=commitdiff;h=180958291462f38154916103a6a4bdeb852e6cc3 *** Bug 206678 has been marked as a duplicate of this bug. *** |