ersions.
I found that to support older autoconf versions, it was useful to put
overrides into conditional blocks like this:
m4_if(m4_version_compare(m4_PACKAGE_VERSION,[2.70]),[-1],
[m4_include([m4/ac_fc_module_output_flag.m4])])
Regards, Thomas
--
Thomas Jahns
HPC-Gruppe
Abteilung Anwendungsso
On 09/14/18 22:06, A.Timmermans wrote:
incorrect, does not compile:
LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@
I'm pretty confident that's the correct way to specify this. Can you provide an
example of what exactly is going wrong? A typical error is to erroneously pu
On 09/15/17 11:17, Mathieu Lirzin wrote:
Instead of preemptively adding possible future version of Python that
hopefully would be released, I would prefer a solution that removes the
need to hard-code them.
WDYT?
Why not parse PATH and filter what pathelem/python* returns for a pattern like
p
4/automake@1.14.1-56e69c6c/share/aclocal-'
. $APIVERSION);
Please see the attached (passes make check on Debian x64, but otherwise
untested) patch
Thomas
--
Thomas Jahns
HD(CP)^2
Abteilung Anwendungssoftware
Deutsches Klimarechenzentrum GmbH
Bundesstraße 45a • D-20146 Hamburg • Germany
Phone: +49
