Subject: Re: poor error reporting when ld.so is missing
To: None <p99dreyf@criens.u-psud.fr>
From: Ben Harris <bjh21@netbsd.org>
List: tech-kern
Date: 04/16/2001 12:10:34
In article <1erxkx8.1wljwfn1ty2u10M%p99dreyf@criens.u-psud.fr> you write:
>We have exactly the same problem for native NetBSD dynamic binaries. Try
>moving /usr/libexec/ld.elf_so, and run a dynamically linked program (gcc
>for instance). The error you get does not tell you what is wrong.
>
>There is nothing in errno.h such as "can't find ld.so". Should we use an
>existing error code (and which one is revelant here), or should we add a
>new one? I beleive adding an errno is not a good ifdea for portability
>reason. Is there any other way of doing it?
I'm inclined to feel that following the behaviour of shell scripts whose
interpreter is missing, and returning ENOENT (or whatever else we get when
we try to access ld.so) would be a sensible compromise.
--
Ben Harris <bjh21@netbsd.org>
Portmaster, NetBSD/arm26 <URL:http://www.netbsd.org/Ports/arm26/>