From: Luca Barbieri <luca.barbieri@gmail.com>
To: Olaf van der Spek <olafvdspek@gmail.com>
Cc: drepper@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: execve() returns ENOENT when ld-linux.so isn't found
Date: Thu, 25 Mar 2010 22:00:49 +0100 [thread overview]
Message-ID: <ff13bc9a1003251400ted1993ao73c15ee86e3e717a@mail.gmail.com> (raw)
In-Reply-To: <b2cc26e41003251229w5d266c18gd17fdcf404136bd7@mail.gmail.com>
POSIX 2008 says, for exec*:
[ENOENT]
A component of path or file does not name an existing file or path
or file is an empty string.
[ENOEXEC]
The new process image file has the appropriate access permission
but has an unrecognized format.
[EINVAL]
The new process image file has appropriate privileges and has a
recognized executable binary format, but the system does not support
execution of a file with this format.
None of these perfectly fit, but EINVAL seems the closest.
Note that ENOENT only specifies that the error happens for "not found"
problems in the function argument itself, so it is not really more
correct than the others.
Linux also defines ELIBACC (for a.out I believe):
#define ELIBACC 79 /* Can not access a needed shared library */
This also seems a possible candidate.
Not sure if it is safe to change this though, or what other systems do.
next prev parent reply other threads:[~2010-03-25 21:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b2cc26e41003241537h228028c4n1374f4b042175885@mail.gmail.com>
2010-03-24 22:45 ` drepper
2010-03-25 19:29 ` Olaf van der Spek
2010-03-25 21:00 ` Luca Barbieri [this message]
2010-03-26 11:56 ` Ulrich Drepper
2010-03-26 18:40 ` Olaf van der Spek
2010-03-26 21:06 ` Luca Barbieri
2010-03-26 21:15 ` Ulrich Drepper
2010-03-27 11:50 ` Olaf van der Spek
2010-03-27 12:05 ` Ulrich Drepper
2010-03-29 14:40 ` Olaf van der Spek
2010-03-29 14:57 ` Ulrich Drepper
2010-03-29 16:00 ` Andreas Schwab
2010-03-31 19:36 ` Olaf van der Spek
2010-03-27 14:51 ` Luca Barbieri
2010-03-18 14:42 Olaf van der Spek
2010-03-24 13:35 ` Olaf van der Spek
2010-03-24 13:49 ` drepper
2010-03-24 22:10 ` Olaf van der Spek
2010-03-24 22:35 ` drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff13bc9a1003251400ted1993ao73c15ee86e3e717a@mail.gmail.com \
--to=luca.barbieri@gmail.com \
--cc=drepper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olafvdspek@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®