[prev in list] [next in list] [prev in thread] [next in thread] 

List:       autoconf-bug
Subject:    Re: automake 2.5x and SunOS don't seem to mix
From:       Aharon Robbins <arnold () skeeve ! com>
Date:       2002-10-22 11:28:48
Message-ID: 200210221128.g9MBSmR04229 () skeeve ! com
[Download RAW message or body]

As it's autoconf that produces configure, and it's configure that's
not working, I believe it's an autoconf bug.

I'll get the config.log for you. Should I send it to the list?

Arnold

> To: Aharon Robbins <arnold@skeeve.com>
> Cc: bug-autoconf@gnu.org
> Subject: Re: automake 2.5x and SunOS don't seem to mix
> From: Akim Demaille <akim@epita.fr>
> Date: 22 Oct 2002 09:45:14 +0200
>
> Hi Aharon,
>
> | I have this report from a pretester for my gawk releases.  The
> | most recent one used automake 2.53 or 2.54 (I don't remember which)
> | and breaks on SunOS (I think 2.54).
>
> Could make it clear whether you have a problem with Autoconf (2.5x) or
> Automake (1.x)?
>
> | Akim or someone else please contact me offline for download info
> | on the tarball, I'm not ready for the world to get at it yet.
> | 
> | Here's the report.
> | 
> | Thanks,
> | 
> | Arnold
> | 
> | > Date: Tue, 15 Oct 2002 19:02:36 -0700 (PDT)
> | > From: Scott Deifik <scottd@amgen.com>
> | > To: arnold@skeeve.com
> | > Subject: Re: new gawk test release available
> | >
> | > On SunOS, configure for gawk-3.1.1e says: "error: C compiler cannot
> | > create executables"
> | >
> | > However, cc works:
> | >
> | > $ 
> | > $ rm tmp
> | > $ tmp
> | > tmp: not found
> | > $ cat tmp.c
> | > #include <stdio.h>
> | >
> | > main()
> | > {
> | >     printf( "Hello\n" );
> | > }
> | > $ cc -o tmp tmp.c
> | > $ tmp
> | > Hello
> | > $ 
> | >
> | >
> | > Running make (after configure) says:
> | >
> | > >make
> | > make: Fatal error: No arguments to build
>
> Thanks for the log, but this is not what we need.  We need you to do
> what configure said:
>
> > configure: error: C compiler cannot create executables
> > check `config.log' for details.
>
> i.e., to look at config.log and understand why configure said the
> compiler is broken.  Everything is in there.
>



[prev in list] [next in list] [prev in thread] [next in thread]