GNU bug report logs - #12094
check failure on AIXv7.1 / xlc

Previous Next

Package: libtool;

Reported by: Jez Wain <JEZ.WAIN <at> BULL.NET>

Date: Mon, 30 Jul 2012 16:47:02 UTC

Severity: normal

To reply to this bug, email your comments to 12094 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-libtool <at> gnu.org:
bug#12094; Package libtool. (Mon, 30 Jul 2012 16:47:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Jez Wain <JEZ.WAIN <at> BULL.NET>:
New bug report received and forwarded. Copy sent to bug-libtool <at> gnu.org. (Mon, 30 Jul 2012 16:47:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jez Wain <JEZ.WAIN <at> BULL.NET>
To: bug-libtool <at> gnu.org
Subject: check failure on AIXv7.1 / xlc
Date: Mon, 30 Jul 2012 17:40:20 +0200
[Message part 1 (text/plain, inline)]
I built libtool on AIXv7.1, POWER7 using xlc compiler.

The configure and make completed without error, but "make check" produced 4 errors.

====================================
4 of 102 tests failed
(4 tests were not run)
See ./test-suite.log
Please report to bug-libtool <at> gnu.org
====================================
  

I used the following configure command:

LDFLAGS="-L/usr/local/lib" LIBS="-lmass" CXX=CC=xlc_r CFLAGS="-O2 -qtune=auto -qarch=auto -qcache=auto -I/usr/local/include" ./configure

Here as requested in the error message, is the test-suite.log file.

  Jez Wain


[Message part 2 (text/html, inline)]
[test-suite.log (application/octet-stream, attachment)]
[Message part 4 (text/html, inline)]

Information forwarded to bug-libtool <at> gnu.org:
bug#12094; Package libtool. (Mon, 30 Jul 2012 23:04:02 GMT) Full text and rfc822 format available.

Message #8 received at 12094 <at> debbugs.gnu.org (full text, mbox):

From: Peter Rosin <peda <at> lysator.liu.se>
To: Jez Wain <JEZ.WAIN <at> BULL.NET>
Cc: 12094 <at> debbugs.gnu.org
Subject: Re: bug#12094: check failure on AIXv7.1 / xlc
Date: Tue, 31 Jul 2012 00:57:19 +0200
On 2012-07-30 17:40, Jez Wain wrote:
> I built libtool on AIXv7.1, POWER7 using xlc compiler.
> 
> The configure and make completed without error, but "make check" produced 4 errors.
> 
> ====================================
> 4 of 102 tests failed
> (4 tests were not run)
> See ./test-suite.log
> Please report to bug-libtool <at> gnu.org <mailto:bug-libtool <at> gnu.org>
> ====================================
> 
> I used the following configure command:
> 
> LDFLAGS="-L/usr/local/lib" LIBS="-lmass" CXX=CC=xlc_r CFLAGS="-O2 -qtune=auto 
> -qarch=auto -qcache=auto -I/usr/local/include" ./configure
> 
> Here as requested in the error message, is the test-suite.log file.

The CXX=CC=xlc_r part is the culprit, did you mean CXX=xlc_r CC=xlc_r,
or perhaps only CXX=xlc_r or perhaps CXX=$CC o something?

Anyway, that's where you should start looking.

Cheers,
Peter




Information forwarded to bug-libtool <at> gnu.org:
bug#12094; Package libtool. (Tue, 31 Jul 2012 16:31:02 GMT) Full text and rfc822 format available.

Message #11 received at 12094 <at> debbugs.gnu.org (full text, mbox):

From: Peter Rosin <peda <at> lysator.liu.se>
To: Jez Wain <jez.wain <at> bull.net>
Cc: 12094 <at> debbugs.gnu.org
Subject: Re: bug#12094: check failure on AIXv7.1 / xlc
Date: Tue, 31 Jul 2012 18:23:47 +0200
Hi Jez,

Please keep the list in CC:, or you'll be stuck with my help only.

On 2012-07-31 15:17, Jez Wain wrote:
> Peter,
> 
> Thanks for the prompt reply and well spotted, for the configuration error - I'd 
> looked at it a couple of times, feeling that something was awry, but staring at 
> it too intently, I couldn't spot it.
> 
> However this is not the cause of the failure.  With a corrected configure command:
> 
> LDFLAGS="-L/usr/local/lib" LIBS="-lmass" CXX=xlC CC=xlc_r CFLAGS="-O2 
> -qtune=auto -qarch=auto -qcache=auto -I/usr/local/include" ./configure
> 
> The "make check" still concludes with:
> 
> ====================================
> 4 of 102 tests failed
> (4 tests were not run)
> See ./test-suite.log
> Please report to bug-libtool <at> gnu.org <mailto:bug-libtool <at> gnu.org>
> ====================================
> make[4]: *** [test-suite.log] Error 1
> 
> I've attached the new test-suite.log to this mail, but, to my untrained eye, it 
> looks similar to the one I sent yesterday.

Yes, it's similar.  Yesterday you had this failure:

/bin/sh ./libtool --tag=CXX   --mode=compile CC=xlc_r -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"tagdemo\ 1.0\" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I.  -I./../..    -c -o foo.lo foo.cpp
libtool: compile:  CC=xlc_r -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" "-DPACKAGE_STRING=\"tagdemo 1.0\"" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I. -I./../.. -c foo.cpp
./libtool[11]: -DPACKAGE_NAME="tagdemo":  not found

You told libtool that the C++ compiler is "CC=xlc_r", but that looks like
an assignment, and -DPACKAGE_NAME="tagdemo" is taken as the C++ compiler
instead.  Things go downhill quickly after that.

And now you have this failure:

/bin/sh ./libtool --tag=CXX   --mode=compile xlC -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"tagdemo\ 1.0\" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I.  -I./../..    -c -o foo.lo foo.cpp
libtool: compile:  xlC -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" "-DPACKAGE_STRING=\"tagdemo 1.0\"" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I. -I./../.. -c foo.cpp
./libtool[11]: xlC:  not found

Here, you have told libtool that the C++ compiler is "xlC", but libtool
simply cannot find that program.

So, the configure command is still not correct as you are pointing to
things that are not there (or have the wrong permissions).

Cheers,
Peter





Information forwarded to bug-libtool <at> gnu.org:
bug#12094; Package libtool. (Wed, 01 Aug 2012 15:43:01 GMT) Full text and rfc822 format available.

Message #14 received at 12094 <at> debbugs.gnu.org (full text, mbox):

From: Jez Wain <jez.wain <at> bull.net>
To: Peter Rosin <peda <at> lysator.liu.se>
Cc: 12094 <at> debbugs.gnu.org
Subject: Re: bug#12094: check failure on AIXv7.1 / xlc
Date: Wed, 1 Aug 2012 17:34:25 +0200
[Message part 1 (text/plain, inline)]
Peter,

There was indeed a PATH problem, xlC wan't being found.  Once corrected I ran the make check and this produced different errors.  I then ran make clean, reran the ./configure switching off all compiler optimization, and finally make check. Switching off compiler optimization didn't make any difference, make check failed on the same tests.

Attached is testsuite.log (as opposed to yesterday's test-suite.log).  For info, test 75 core dumped.

Jez


[testsuite.log (application/octet-stream, attachment)]
[Message part 3 (text/plain, inline)]

On 31 Jul 2012, at 18:23, Peter Rosin wrote:

> Hi Jez,
> 
> Please keep the list in CC:, or you'll be stuck with my help only.
> 
> On 2012-07-31 15:17, Jez Wain wrote:
>> Peter,
>> 
>> Thanks for the prompt reply and well spotted, for the configuration error - I'd 
>> looked at it a couple of times, feeling that something was awry, but staring at 
>> it too intently, I couldn't spot it.
>> 
>> However this is not the cause of the failure.  With a corrected configure command:
>> 
>> LDFLAGS="-L/usr/local/lib" LIBS="-lmass" CXX=xlC CC=xlc_r CFLAGS="-O2 
>> -qtune=auto -qarch=auto -qcache=auto -I/usr/local/include" ./configure
>> 
>> The "make check" still concludes with:
>> 
>> ====================================
>> 4 of 102 tests failed
>> (4 tests were not run)
>> See ./test-suite.log
>> Please report to bug-libtool <at> gnu.org <mailto:bug-libtool <at> gnu.org>
>> ====================================
>> make[4]: *** [test-suite.log] Error 1
>> 
>> I've attached the new test-suite.log to this mail, but, to my untrained eye, it 
>> looks similar to the one I sent yesterday.
> 
> Yes, it's similar.  Yesterday you had this failure:
> 
> /bin/sh ./libtool --tag=CXX   --mode=compile CC=xlc_r -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"tagdemo\ 1.0\" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I.  -I./../..    -c -o foo.lo foo.cpp
> libtool: compile:  CC=xlc_r -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" "-DPACKAGE_STRING=\"tagdemo 1.0\"" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I. -I./../.. -c foo.cpp
> ./libtool[11]: -DPACKAGE_NAME="tagdemo":  not found
> 
> You told libtool that the C++ compiler is "CC=xlc_r", but that looks like
> an assignment, and -DPACKAGE_NAME="tagdemo" is taken as the C++ compiler
> instead.  Things go downhill quickly after that.
> 
> And now you have this failure:
> 
> /bin/sh ./libtool --tag=CXX   --mode=compile xlC -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" -DPACKAGE_STRING=\"tagdemo\ 1.0\" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I.  -I./../..    -c -o foo.lo foo.cpp
> libtool: compile:  xlC -DPACKAGE_NAME=\"tagdemo\" -DPACKAGE_TARNAME=\"tagdemo\" -DPACKAGE_VERSION=\"1.0\" "-DPACKAGE_STRING=\"tagdemo 1.0\"" -DPACKAGE_BUGREPORT=\"bug-libtool <at> gnu.org\" -DPACKAGE_URL=\"\" -DPACKAGE=\"tagdemo\" -DVERSION=\"1.0\" -DLT_OBJDIR=\".libs/\" -I. -I./../.. -c foo.cpp
> ./libtool[11]: xlC:  not found
> 
> Here, you have told libtool that the C++ compiler is "xlC", but libtool
> simply cannot find that program.
> 
> So, the configure command is still not correct as you are pointing to
> things that are not there (or have the wrong permissions).
> 
> Cheers,
> Peter
> 


This bug report was last modified 13 years and 19 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.