GNU bug report logs - #15845
[GNU Libtool 2.4.2] testsuite: 55 95 96 97 107 115 failed

Previous Next

Package: libtool;

Reported by: Андрей Новиков <stalkien <at> rambler.ru>

Date: Sat, 9 Nov 2013 23:18:01 UTC

Severity: normal

To reply to this bug, email your comments to 15845 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#15845; Package libtool. (Sat, 09 Nov 2013 23:18:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Андрей Новиков <stalkien <at> rambler.ru>:
New bug report received and forwarded. Copy sent to bug-libtool <at> gnu.org. (Sat, 09 Nov 2013 23:18:03 GMT) Full text and rfc822 format available.

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

From: Андрей Новиков <stalkien <at> rambler.ru>
To: kristos84 <at> mail.ru, bug-libtool <at> gnu.org
Subject: [GNU Libtool 2.4.2] testsuite: 55 95 96 97 107 115 failed
Date: Sun, 10 Nov 2013 02:19:54 +0400
[Message part 1 (text/plain, inline)]
Current MinGW+MSYS versions deployed on my Wintel have the libtool [2.4.1-msys ??
I doubt: really only usual libtool-2.4-1-mingw32-bin.tar.lzma ],
GCC 4.8.1.
Before a build of the 2.4.2 [for MinGW - not for MSYS] (i.e. the one for this
report): I already decided to use (even for a build and hence for this build)
the libtool file (in /mingw/bin) with my manual correction: I saw the strange
[for the presence of GCC 4.8.1 deployed] script - working,
but inside it there were 4.5.0 paths instead of 4.8.1 (and this is not strange
for the libtool-2.4-1-mingw32-bin.tar.lzma , but only for the current
MinGW+MSYS).
I almost ignore this hand-made file, but here it is among the attachment.
The build of the 2.4.2 that I mention above was successful, but here the .log -
more important file, of cource - is among the attachment.

(One can see
sys_lib_search_path_spec="c:/tingw/lib/gcc/mingw32/4.8.1 c:/tingw/lib/gcc
c:/tingw/mingw32/lib c:/tingw/lib "
and
compiler_lib_search_dirs="c:/tingw/bin/../lib/gcc/mingw32/4.8.1
c:/tingw/bin/../lib/gcc
c:/tingw/bin/../lib/gcc/mingw32/4.8.1/../../../../mingw32/lib
c:/tingw/bin/../lib/gcc/mingw32/4.8.1/../../.."
in the 312.96KB file of the 2.4.2 build
- the "TinGW" substrings are due to my allusion to tin plague under a frost:/)

Best regards, while you can be giving an advice what a libtool without any
hand-made file must become a mean for my case.
[Message part 2 (text/html, inline)]
[config.log (application/octet-stream, attachment)]
[config.status (application/octet-stream, attachment)]
[test-suite.log (application/octet-stream, attachment)]
[libtool (application/octet-stream, attachment)]
[libtool (application/octet-stream, attachment)]
[testsuite.log (application/octet-stream, attachment)]
[testsuite.log (application/octet-stream, attachment)]
[testsuite.log (application/octet-stream, attachment)]
[testsuite.log (application/octet-stream, attachment)]
[testsuite.log (application/octet-stream, attachment)]
[testsuite.log (application/octet-stream, attachment)]

This bug report was last modified 11 years and 275 days ago.

Previous Next


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