On 1/1/13 2:49 PM, Aharon Robbins wrote:
> In article <mailman.16481.1357062499.855.bug-b...@gnu.org>,
> Michael Williamson <michael.h.william...@gmail.com> wrote:
>> Hi,
>>
>> I have a complaint. Apparently, when unknowingly attempting to run a
>> 32-bit executable file on a 64-bit computer, bash gives the error message
>> "No such file or directory". That error message is baffling and frustratingly
>> unhelpful. Is it possible for bash to provide a better error message
>> in this case?
>>
>> Thanks,
>> -Mike
>
> It's not Bash. That is the error returned from the OS in errno when
> it tries to do an exec(2) of the file. Bash merely translates the
> error into words.
FWIW, the file in question that's not found is either the 32-bit version
of the loader or one of the required 32-bit libraries, not the binary
itself.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
