On 30 May 2000, Alexandre Oliva wrote:
> On May 29, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>
> > How much interest would there be in adding Java to the
> > autoconf supported languages?
>
> It'd certainly be appreciated. But we have to be careful, since there
> are two (three?) kinds of Ja
As IDL files use standard C preprocessor syntax for dependent
inclusion, is it not possible to wrap the idl compile in depcomp?
My IDL build rules are already structured as suffix rules, with a
small wrapper script around the IDL compiler that uses lockfile(1) to
prevent two targets (e.g. client
I'd like to make a small suggestion for autoconf -- it would be helpful
in debugging configuration problems if the output that is displayed on
the screen during configuration:
checking for gcc... cc
checking whether the C compiler (cc -O2 -g ) works... yes
checking whether the C compiler (c
`fc' is the f77-like script from the f2c distribution.
2000-05-31 Dave Love <[EMAIL PROTECTED]>
* aclang.m4 (AC_PROG_F77): Check for f95 and fc too.
Index: aclang.m4
===
RCS file: /cvs/autoconf/aclang.m4,v
retrieving revi
On Wed, 31 May 2000, Keith Bostic wrote:
> I'd like to make a small suggestion for autoconf -- it would be helpful
> in debugging configuration problems if the output that is displayed on
> the screen during configuration:
>
> checking for gcc... cc
> checking whether the C compiler (cc -O2
Keith Bostic writes:
> I'd like to make a small suggestion for autoconf -- it would be
> helpful in debugging configuration problems if the output that is
> displayed on the screen during configuration were also copied into the
> config.log output.
This is already the case in the the development
Keith Bostic wrote:
> I'd like to make a small suggestion for autoconf -- it would be helpful
> in debugging configuration problems if the output that is displayed on
> the screen during configuration [...] were also copied into the
>config.log output.
That feature has already been incorporated i
>> I would also encourage putting the source for all test programs into the
>> config.log file too, not just the failed ones. I don't know about other
>> folks, but we use config.log for the sole purpose of debugging problems,
>> and so the more information we can get in that file, the better off
Dave Love wrote:
> * aclang.m4 (AC_PROG_F77): Check for f95 and fc too.
> [...]
> m4_default([$1], [g77 f77 xlf cf77 fl32 fort77 f90 xlf90 f95 fc]))
Is "fc" an F95 compiler? F90? F77? I ask because I think all of the
Fortran 77 compilers should be checked before the F90 compilers, which
should
Tom Tromey <[EMAIL PROTECTED]> writes:
> > "Diego" == Diego Sevilla Ruiz <[EMAIL PROTECTED]> writes:
>
> Diego> IDL_DEPS(anyfile.idl)
>
> There was a discussion on this on the automake list in the past.
> I don't remember the outcome.
>
> I think the best approach would be to have an autoc
I'd like to move the "-c" argument usually attached to the end of the
definition of "INSTALL" over to those "INSTALL_*" macros that need it.
This has bugged me for a long time and I finally encountered a real
situation where I couldn't easily hack around the problem.
It turns out that some versi
> "Alex" == Alex Hornby <[EMAIL PROTECTED]> writes:
Alex> As IDL files use standard C preprocessor syntax for dependent
Alex> inclusion, is it not possible to wrap the idl compile in
Alex> depcomp?
Interesting idea. I thought different IDL compilers generated
different output file names, th
Tom Tromey wrote:
> "Alex" == Alex Hornby <[EMAIL PROTECTED]> writes:
Alex> As IDL files use standard C preprocessor syntax for dependent
Alex> inclusion, is it not possible to wrap the idl compile in
Alex> depcomp?
Interesting idea. I thought different IDL compilers generated
13 matches
Mail list logo
