|
From: | Thomas Jahns |
Subject: | bug#15681: automake 1.14, make check failures on AIX |
Date: | Tue, 22 Oct 2013 13:56:46 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130922 Icedove/17.0.9 |
Hello, I've built automake 1.14 on our AIX 6.1 system, there are some bugs creeping up. Two (libtool7 and libtool9) are more of a libtool affair which I've filed separately to the libtool bug list. The others are problems with automake itself it seems. Those which were related to t/get-sysconf.sh I already fixed. Please find the attached patch which handles a problem with the attempt to call lex with option --version. AIX lex gives the following behaviour when called as lex --version: $ lex --version 0: Warning: 1285-300 The - flag is not valid. 0: Warning: 1285-300 The e flag is not valid. 0: Warning: 1285-339 Ratfor is not supported with lex. 0: Warning: 1285-300 The s flag is not valid. 0: Warning: 1285-300 The i flag is not valid. 0: Warning: 1285-300 The o flag is not valid. At this point the program hangs waiting for input on stdin. When entering C-D and line-feed, lex finished: ^D Error: 1285-340 The rules section delimiter is missing. $ The one in t/lex-clean-cxx results from mainfoo.cc not correctly declaring yylex as extern "C". I therefore propose to change the declaration in mainfoo.cc accordingly. Please see the attached patch. Unfortunately I don't understand what's tripping up t/lex-line, but I'm quite willing to test any suggestion. The same is true for t/tap-signal-w. No idea what's going on there. Regards, Thomas -- Thomas Jahns DKRZ GmbH, Department: Application software Deutsches Klimarechenzentrum Bundesstraße 45a D-20146 Hamburg Phone: +49-40-460094-151 Fax: +49-40-460094-270 Email: Thomas Jahns <address@hidden>
test-suite.log.gz
Description: GNU Zip compressed data
automake-1.14-t-lex-clean-cxx.sh.patch
Description: Text Data
automake-1.14-t-get-sysconf.sh.patch
Description: Text Data
smime.p7s
Description: S/MIME Cryptographic Signature
[Prev in Thread] | Current Thread | [Next in Thread] |