[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: No such file or directory

From: Aharon Robbins
Subject: Re: No such file or directory
Date: Tue, 1 Jan 2013 19:49:14 +0000 (UTC)

In article <address@hidden>,
Michael Williamson  <address@hidden> wrote:
>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?

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.

Depending on the distro, it's usually not too hard to install the 32 bit
compatibility files to support 32 bit executables.  The "enterprise"
distibutions tend to do that by default, whereas the more free ones
(Fedora, Ubuntu, ...) require that you do it yourself.

I agree, it's confusing.  But it's a decision made by the kernel guys,
not Bash.


Aharon (Arnold) Robbins                         arnold AT skeeve DOT com
P.O. Box 354            Home Phone: +972  8 979-0381
Nof Ayalon              Cell Phone: +972 50 729-7545
D.N. Shimshon 99785     ISRAEL

reply via email to

[Prev in Thread] Current Thread [Next in Thread]