On 01/22/2013 11:21 AM, johannes.bie...@hzg.de wrote:
> Finally I solved the problem:
>
> I had flex 2.5.37 installed locally (I have no admin rights)
> but the command 'lex' was still linked to the old flex 2.5.31 version.
>
> So I was using way too old versions of flex and bison and there is
>
Finally I solved the problem:
I had flex 2.5.37 installed locally (I have no admin rights)
but the command 'lex' was still linked to the old flex 2.5.31 version.
So I was using way too old versions of flex and bison and there is no bug in
automake.
Although it would be helpful if configure would
bison v2.4 solved the problem:
PASS: t/yacc-bison-skeleton-cxx.sh
However I still get 2 FAILS from lex-clean-cxx and lex-depend-cxx
(using flex 2.5.37 now)
+ cp config.status config.sav
+ make
c++ -DPACKAGE_NAME=\"lex-clean-cxx\" -DPACKAGE_TARNAME=\"lex-clean-cxx\"
-DPACKAGE_VERSION=\"1.0\"
Thanks for getting back at me so quickly.
On 01/21/2013 03:27 PM, johannes.bie...@hzg.de wrote:
>> Weird, it seems Flex is not respecting the "YY_NO_UNISTD_H" #define
>> given in 'parsefoo.lxx'. Which version of Flex are you using?
>
> flex --version
> flex 2.5.31
>
Yep, that's old; according to
>Weird, it seems Flex is not respecting the "YY_NO_UNISTD_H" #define
>given in 'parsefoo.lxx'. Which version of Flex are you using?
flex --version
flex 2.5.31
Helmholtz-Zentrum Geesthacht
Zentrum für Material- und Küstenforschung GmbH
Max-Planck-Straße 1 I 21502 Geesthacht I Deutschland/Germany
tags 13436 + moreinfo
severity 13436 minor
thanks
On 01/14/2013 05:08 PM, johannes.bie...@hzg.de wrote:
> Hi,
>
Hello Johannes. Thanks for the report, and sorry for the delay.
> I compiled automake 1.12.6 and got 3 fails when doing make check.
> I tried it with v1.13.1 and got the same results.
Hi,
I compiled automake 1.12.6 and got 3 fails when doing make check.
I tried it with v1.13.1 and got the same results.
echo $MACHTYPE
x86_64-suse-linux
I tried to use gcc + ifort
and gcc + gfortran
=
=
=
=
Testsuite summar