Permission denied on a.out in ./configure

[Clayton Daley]

No need to belabor the topic. @Torbjorn was right.  I thought I had
uploaded a modified configure when the program started working, but
something else in the environment had changed.

More importantly, if I bypass the "a.out" check by a modification that
actually works (e.g. "test -s a.out"), I'm later told "configure: error:
cannot run C compiled programs." While the original compiler error isn't
strictly correct, it masks a different fatal error so there's little to be
gained by fixing it (except saving the next guy the trouble of coming to
the "execute permissions" conclusion using the log).

Clayton Daley

On Thu, Sep 18, 2014 at 9:20 PM, Torbjörn Granlund <tg at gmplib.org> wrote:

> Clayton Daley <clayton.daley at gmail.com> writes:
>
>   Incidentally, a fix at my end was to replace "./a.out" with "sh ./a.out"
> in
>   configure.  The rest of the process ran fine (except, the final make
>
> Wild.
>
>   install since I don't have permission).  The "better" approach -- of
> course
>   -- would have been to extend the lines that check "./a.out" with
> additional
>   "or"s for the same files using "sh" (but I didn't need to preserve the
>   original checks).
>
> That would seem very strange, since a.out is an executable, while a
> command like "sh foo" means that foo is a shell script.
>
>
> --
> Torbjörn
> Please encrypt, key id 0xC8601622
>