[...]
| The problem is that Intel's C++ _accepts_ these flags and
| only emits a warning. This might confuse the autotools here:
Yep.
| make[1]: Entering directory `/work/tresca/markus/DORIS/doris-0.0.1'
| if icpc -DHAVE_CONFIG_H -I. -I. -I. -I. -I./src -I/opt/boost-1.29.0 -I/work/tr
| esca/ma
>>> "jlm" == jlm <[EMAIL PROTECTED]> writes:
[...]
jlm> automake-1.5: configure.ac: `AM_INIT_AUTOMAKE' must be used
[...]
jlm> AM_INIT_AUTOMAKE([no-define])
You need Automake 1.6 or greater to use this syntax.
If for some reason you want to stick to 1.5, use
AM_INIT_AUTOMAKE([libgtkbonus]
>>> "Phil" == Phil Edwards <[EMAIL PROTECTED]> writes:
Phil> When AUTOMAKE_OPTIONS contains dejagnu, one of the generated rules is
Phil> check-am:
Phil> $(MAKE) $(AM_MAKEFLAGS) check-DEJAGNU
Phil> I could have sworn that at some time in the not-too-distant past, the -k
Phil> flag would also
>>> "gd" == Guido Draheim <[EMAIL PROTECTED]> writes:
[...]
gd> (a) per file compile flags:
gd> - it's an faq and later automake supports it natively
This has yet to be implemented (any taker?). What Automake
supports presently is per-target flags. The usual way
to emulate per-object flags i
jlm wrote:
I'm using automake version 1.5. I'm getting an error with automake, and
I can't figure out why. When I run automake, I get this error:
automake-1.5: configure.ac: `AM_INIT_AUTOMAKE' must be used
But I am using AM_INIT_AUTOMAKE, here's the top of my configure.ac file:
#Process this file
I'm using automake version 1.5. I'm getting an error with automake, and
I can't figure out why. When I run automake, I get this error:
automake-1.5: configure.ac: `AM_INIT_AUTOMAKE' must be used
But I am using AM_INIT_AUTOMAKE, here's the top of my configure.ac file:
#Process this file with autoco
