On Fri, Aug 17, 2001 at 11:50:24PM +0100, Gary V. Vaughan wrote:
> On Friday 17 August 2001 4:49 pm, Akim Demaille wrote:
> > Typically, one can observe that the Autotest snippet contain useless
> > multiple empty lines, which are to be killed, while those in the test
> > values have to be kept.
>
On Saturday 18 August 2001 10:24 am, [EMAIL PROTECTED] wrote:
> Something like AC_MSG_RESULT(@""@) outputs @\"\"@, not @""@. So the
> quadrigraph is not recognized, and not replaced. I'm not in favor of
> also replacing @\"\"@, but just because it frightens me a bit. If someone
> is convinced t
Hello,
My autoconf version is Autoconf version 2.13; perhaps this bug has
been previously corrected.
In Info, at (autoconf)Compilers and Options and at
(autoconf)Environment Variables, the environment variables examples
don't work.
Instead of
./configure CC=/usr/local2/bin/gcc
it should be
C
> "Steven" == Steven G Johnson <[EMAIL PROTECTED]> writes:
Steven> When linking a program that contains both C and Fortran source
Steven> files, automake uses the Fortran linker. This causes some
Steven> difficulty with the Compaq compilers ('fort' and 'ccc') for
Steven> Alpha (Linux).
Stev
On 18 Aug 2001, Tom Tromey wrote:
> Steven> What is the right thing to do?
>
> Of course I'd prefer the code in automake to remain simple :-).
>
> I think if Fortran compilers differ, then we must test to see what the
> actual Fortran compiler in use does. This means autoconf must decide.
auto
