I was trying to install some our application on Rapsberry PI. I do not why, but sys-fs/static-dev-0.1 came to dependencies on emerge and failed to build I followed the hint, mounted the root system, but if failed again, the same way Reproducible: Always Steps to Reproduce: 1. Raspberry PI, emerge all what is needed, then 2. emerge --update --newuse --deep @world -vq --keep-going -a 3. failed 4. mkdir /tmp/newroot 5. mount -o bind / /tmp/newroot 6. ROOT=/tmp/newroot/ emerge sys-fs/static-dev 7. failed again Actual Results: localhost ~ # mkdir /tmp/newroot localhost ~ # mount -o bind / /tmp/newroot localhost ~ # ROOT=/tmp/newroot/ emerge sys-fs/static-dev * IMPORTANT: 4 news items need reading for repository 'gentoo'. * Use eselect news to read news items. Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-fs/static-dev-0.1 for /tmp/newroot/ >>> Unpacking source... >>> Source unpacked in /var/tmp/portage/sys-fs/static-dev-0.1/work >>> Compiling source in /var/tmp/portage/sys-fs/static-dev-0.1/work ... >>> Source compiled. >>> Test phase [not enabled]: sys-fs/static-dev-0.1 >>> Install static-dev-0.1 into /var/tmp/portage/sys-fs/static-dev-0.1/image/ category sys-fs >>> Completed installing static-dev-0.1 into /var/tmp/portage/sys-fs/static-dev-0.1/image/ >>> Installing (1 of 1) sys-fs/static-dev-0.1 to /tmp/newroot/ * We have detected that you currently use udev or devfs or devtmpfs * and this ebuild cannot install to the same mount-point. * Please reinstall the ebuild (as root) like follows: * * mkdir /tmp/newroot * mount -o bind / /tmp/newroot * ROOT=/tmp/newroot/ emerge sys-fs/static-dev * umount /tmp/newroot * ERROR: sys-fs/static-dev-0.1 failed (preinst phase): * Cannot install on udev/devfs tmpfs. * * Call stack: * ebuild.sh, line 93: Called pkg_preinst * environment, line 110: Called die * The specific snippet of code: * die "Cannot install on udev/devfs tmpfs."; * * If you need support, post the output of `emerge --info '=sys-fs/static-dev-0.1'`, * the complete build log and the output of `emerge -pqv '=sys-fs/static-dev-0.1'`. * The complete build log is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/environment'. * Working directory: '/usr/lib/portage/pym' * S: '/var/tmp/portage/sys-fs/static-dev-0.1/work/static-dev-0.1' !!! FAILED preinst: 1 >>> Failed to install sys-fs/static-dev-0.1 to /tmp/newroot/, Log file: >>> '/var/tmp/portage/sys-fs/static-dev-0.1/temp/build.log' localhost ~ # mount rootfs on / type rootfs (rw) /dev/root on / type ext3 (rw,relatime,data=ordered) devtmpfs on /dev type devtmpfs (rw,relatime,size=216120k,nr_inodes=54030,mode=755) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620) shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) cgroup_root on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755) openrc on /sys/fs/cgroup/openrc type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/lib/rc/sh/cgroup-release-agent.sh,name=openrc) cpu on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu) cpuacct on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct) devices on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) freezer on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) blkio on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) / on /tmp/newroot type none (rw,bind) /var/tmp/portage/sys-fs/static-dev-0.1/temp/build.log : ^[[32;01m * ^[[39;49;00mPackage: sys-fs/static-dev-0.1 ^[[32;01m * ^[[39;49;00mRepository: gentoo ^[[32;01m * ^[[39;49;00mMaintainer: base-system@gentoo.org ^[[32;01m * ^[[39;49;00mUSE: arm elibc_glibc kernel_linux userland_GNU ^[[32;01m * ^[[39;49;00mFEATURES: preserve-libs sandbox >>> Unpacking source... >>> Source unpacked in /var/tmp/portage/sys-fs/static-dev-0.1/work >>> Compiling source in /var/tmp/portage/sys-fs/static-dev-0.1/work ... >>> Source compiled. >>> Test phase [not enabled]: sys-fs/static-dev-0.1 >>> Install static-dev-0.1 into /var/tmp/portage/sys-fs/static-dev-0.1/image/ category sys-fs >>> Completed installing static-dev-0.1 into /var/tmp/portage/sys-fs/static-dev-0.1/image/ ^[[31;01m*^[[0m We have detected that you currently use udev or devfs or devtmpfs ^[[31;01m*^[[0m and this ebuild cannot install to the same mount-point. ^[[31;01m*^[[0m Please reinstall the ebuild (as root) like follows: ^[[31;01m*^[[0m ^[[31;01m*^[[0m mkdir /tmp/newroot ^[[31;01m*^[[0m mount -o bind / /tmp/newroot ^[[31;01m*^[[0m ROOT=/tmp/newroot/ emerge sys-fs/static-dev ^[[31;01m*^[[0m umount /tmp/newroot ^[[31;01m*^[[0m ERROR: sys-fs/static-dev-0.1 failed (preinst phase): ^[[31;01m*^[[0m Cannot install on udev/devfs tmpfs. ^[[31;01m*^[[0m ^[[31;01m*^[[0m Call stack: ^[[31;01m*^[[0m ebuild.sh, line 93: Called pkg_preinst ^[[31;01m*^[[0m environment, line 110: Called die ^[[31;01m*^[[0m The specific snippet of code: ^[[31;01m*^[[0m die "Cannot install on udev/devfs tmpfs."; ^[[31;01m*^[[0m ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=sys-fs/static-dev-0.1'`, ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=sys-fs/static-dev-0.1'`. ^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/build.log'. ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/sys-fs/static-dev-0.1/temp/environment'. ^[[31;01m*^[[0m Working directory: '/usr/lib/portage/pym' ^[[31;01m*^[[0m S: '/var/tmp/portage/sys-fs/static-dev-0.1/work/static-dev-0.1' !!! FAILED preinst: 1
(In reply to gilhad from comment #0) > I do not why, but sys-fs/static-dev-0.1 came to dependencies on emerge > and failed to build You don't know why you are installing sys-fs/static-dev? Then you don't want it, but sys-fs/udev (or sys-apps/systemd) instead. It says: > * We have detected that you currently use udev or devfs or devtmpfs > * and this ebuild cannot install to the same mount-point. And your mount output says: > devtmpfs on /dev type devtmpfs So you are enabling CONFIG_DEVTMPFS=y in the kernel and wonder why static-dev is failing to emerge? Then read again from above and do the math. But as said, if you don't know why emerge is pulling static-dev in... Then you should find out, and make it stop doing that. You don't want static-dev unless you really *want* it, it's no way the default.
And in case you *really* want static-dev, and the check for /dev mounted as devtmpfs is a problem, there is bug 469620 for it already
