Ugh.
The problem here is that if you execve() a binary whose interpreter is
missing, then the kernel just gives you ENOENT. I'm not sure that
dropping in stub interpreters for anything that might need to exist is a
good solution here.
Maybe this would be better fixed at the command-not-found level. It
could check whether the binary is actually present on $PATH, and then
hunt around to tell you which package you need to install in order to
get hold of its interpreter.
** Changed in: command-not-found (Ubuntu)
Sourcepackagename: glibc => command-not-found
Importance: Undecided => Wishlist
Status: New => Confirmed
--
libc6 integration gives way wrong error message to libc5 binaries.
https://bugs.launchpad.net/bugs/335666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
