Summary: | sys-fs/udev-052: udevstart uses absolute link | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sascha Silbe <sascha-gentoo-bugzilla> |
Component: | [OLD] Core system | Assignee: | Greg Kroah-Hartman (RETIRED) <gregkh> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch against udev-052.ebuild to make udevstart symlink relative |
Description
Sascha Silbe
2005-02-22 16:10:23 UTC
Well, after examining it further, I saw that the problem isn't that udevstart isn't linked statically. It's a symbolic link, so it's not linked at all (no pun intended :) ). The reason for ldd to show it as statically linked is that it uses an absolute path, thus pointing to the binary installed on the host system. Is there a reason to use an absolute link instead of a relative one (like e.g. util-linux uses)? Just the way I wrote the ebuild. If you don't like it as such, submit a patch to the ebuild :) Created attachment 51973 [details, diff]
patch against udev-052.ebuild to make udevstart symlink relative
|