Re: Obscure configure bug

[Mats Bengtsson]

Jan Nieuwenhuizen wrote:
> Mats Bengtsson <address@hidden> writes:
>
>
> > I happened to have a file called a.dvi in my building directory
> > and then configure stopped with a message that my C compiler didn't
> > produce any working code. I have autoconf version 2.50 here, haven't
> > tried any other versions.
>
>
> Silly question: Are you sure there was not a file `a.out' too?

Positive!
----------------------------------------
>rm a.*
>touch a.dvi
>./configure
checking build system type... i686-pc-linux-gnu
checking Package... LILYPOND
checking builddir... /home.local/matsb/Private/lilypond
checking for stepmake... ./stepmake  (${prefix}/share/stepmake not found)
checking host system type... i686-pc-linux-gnu
checking for gmake... gmake
checking for find... find
checking for tar... tar
checking for bash... /bin/sh
checking for python... python
checking python version... 2.2
checking for python... /mpkg/python/2.2/bin/python
checking for gcc... gcc
checking for C compiler default output... a.dvi
checking whether the C compiler works... configure: error: cannot run C 
compiled programs.
If you meant to cross compile, use `--host'.
>ls a.*
a.dvi
------------------------------------------

I found the following lines in config.log:
------------------------------------------
configure:2209: checking for C compiler default output
configure:2212: gcc   -Wl,-rpath,/home.local/matsb/lib conftest.c  >&5
configure:2215: $? = 0
configure:2238: result: a.dvi
configure:2243: checking whether the C compiler works
configure:2249: ./a.dvi
./configure: ./a.dvi: Permission denied
-------------------------------------------

> > Can someone else confirm this problem?
>
>
> I can confirm the obvious fact that autoconf is broken:
>
>    16:31:17 address@hidden:~/lily
>    $ touch a.out
>    16:31:23 address@hidden:~/lily
>    $ chmod -w a.out
>    16:31:35 address@hidden:~/lily
>    $ clily
>    checking build system type... i686-pc-linux-gnu
>    checking Package... LILYPOND
>    checking builddir... /home/janneke/lily
>    ...
>    checking for C compiler default output... configure: error: C compiler
>    cannot create executables
>    See `config.log' for more details.
>    16:31:39 address@hidden:~/lily

I browsed quickly through the autoconf documentation and tried a
quick search in Google but couldn't find anything directly related.
Maybe I should file a bug report. Especially if anyone can confirm
my results with a.dvi on the latest autoconf version.

   /Mats