Summary: | sys-fs/static-dev-0.1 - We have detected that you currently use udev or devfs or devtmpfs and this ebuild cannot install to the same mount-point. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | gilhad <gilhad> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
gilhad
2013-08-26 20:11:39 UTC
(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 |