libtool ChangeLog NEWS libltdl/Makefile.inc
CVSROOT:/sources/libtool Module name:libtool Changes by: Gary V. Vaughan gary 08/02/01 19:03:56 Modified files: . : ChangeLog NEWS libltdl: Makefile.inc Log message: * libltdl/Makefile.inc (EXTRA_DIST): Now that we're not using Autoconf's AC_SOURCES macro, Automake can't trace our extra source files argz, lt__dirent.c and lt__strl.c. List them manually here to make sure they are distributed. * NEWS: Updated. Reported by Bob Friesenhahn [EMAIL PROTECTED] CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/libtool/ChangeLog?cvsroot=libtoolr1=1.2584r2=1.2585 http://cvs.savannah.gnu.org/viewcvs/libtool/NEWS?cvsroot=libtoolr1=1.216r2=1.217 http://cvs.savannah.gnu.org/viewcvs/libtool/libltdl/Makefile.inc?cvsroot=libtoolr1=1.9r2=1.10 ___ Libtool-commit mailing list Libtool-commit@gnu.org http://lists.gnu.org/mailman/listinfo/libtool-commit
FYI: 353-gary-fix-nonrecursive-libobj-dist
Applied to HEAD as an obvious bugfix. Index: ChangeLog from Gary V. Vaughan [EMAIL PROTECTED] * libltdl/Makefile.inc (EXTRA_DIST): Now that we're not using Autoconf's AC_SOURCES macro, Automake can't trace our extra source files argz, lt__dirent.c and lt__strl.c. List them manually here to make sure they are distributed. * NEWS: Updated. Reported by Bob Friesenhahn [EMAIL PROTECTED] Index: NEWS === RCS file: /sources/libtool/libtool/NEWS,v retrieving revision 1.216 diff -u -u -r1.216 NEWS --- NEWS 31 Jan 2008 16:21:18 - 1.216 +++ NEWS 1 Feb 2008 19:03:08 - @@ -1,5 +1,12 @@ NEWS - list of user-visible changes between releases of GNU Libtool +New in 2.1c: 2012-??-??; CVS version 2.1c, Libtool team: + +* Bug fixes: + + - argz.c, lt__dirent.c and lt__strl.c are correctly distributed with +parent projects using nonrecursive libltdl. + New in 2.1b: 2008-02-01; CVS version 2.1a, Libtool team: * Important incompatible changes and obsoleted features: Index: libltdl/Makefile.inc === RCS file: /sources/libtool/libtool/libltdl/Makefile.inc,v retrieving revision 1.9 diff -u -u -r1.9 Makefile.inc --- libltdl/Makefile.inc 31 Jan 2008 16:21:19 - 1.9 +++ libltdl/Makefile.inc 1 Feb 2008 19:03:08 - @@ -70,6 +70,9 @@ libltdl/ltdl.h \ libltdl/slist.c +EXTRA_DIST += libltdl/lt__dirent.c \ + libltdl/lt__strl.c + libltdl_libltdl_la_CPPFLAGS = -DLTDLOPEN=$(LTDLOPEN) $(AM_CPPFLAGS) libltdl_libltdl_la_LDFLAGS = $(AM_LDFLAGS) $(LTDL_VERSION_INFO) $(LT_DLPREOPEN) libltdl_libltdl_la_LIBADD= $(LTLIBOBJS) @@ -136,7 +139,8 @@ ## --- ## BUILT_SOURCES+= libltdl/$(ARGZ_H) -EXTRA_DIST += libltdl/argz_.h +EXTRA_DIST += libltdl/argz_.h \ +libltdl/argz.c # We need the following in order to create an argz.h when the system # doesn't have one that works with the given compiler. -- ())_. Email me: [EMAIL PROTECTED] ( '/ Read my blog: http://blog.azazil.net / )= ...and my book: http://sources.redhat.com/autobook `(_~)_ _ This patch notification generated by vcsapply version 1.0 http://savannah.gnu.org/projects/cvs-utils pgpdL20nmVxp0.pgp Description: PGP signature
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
Hello Andreas,
* Andreas Schwab wrote on Fri, Feb 01, 2008 at 03:43:25PM CET:
16. convenience.at:69: testing ...
./convenience.at:70: { test -n $CXX test X$CXX != Xno; } || (exit 77)
libtool: compile: g++ -c main1.cpp -o .libs/main1.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: compile: g++ -c a1.cpp -o .libs/a1.o
Thanks for the bug report. Fixed as follows.
The fact that AC_PROG_CXX sets CXX to g++ as a default seems to me like
a bug in Autoconf. The code used gcc as a default up to commit
d9409a1c3c06a015a0fc829989cb1a93c1599cd7
which it had ever since AC_PROG_CXX was added 1994 in commit
8202df5faf642cde4e5b1fa02cd9cc4411a7a477
I'll propose to remove that in Autoconf.
Cheers,
Ralf
2008-02-01 Ralf Wildenhues [EMAIL PROTECTED]
* tests/testsuite.at (LT_AT_TAG): For the CXX tag, if $CXX is
g++, check that `g++ -v' works; AC_PROG_CXX may have set that
as default value even if it found no C++ compiler.
Report by Andreas Schwab.
Index: tests/testsuite.at
===
RCS file: /cvsroot/libtool/libtool/tests/testsuite.at,v
retrieving revision 1.50
diff -u -r1.50 testsuite.at
--- tests/testsuite.at 25 Mar 2007 12:12:43 - 1.50
+++ tests/testsuite.at 1 Feb 2008 19:05:24 -
@@ -1,6 +1,7 @@
# Process with autom4te to create an -*- Autotest -*- test suite.
#
-# Copyright (C) 2004, 2005, 2006, 2007 Free Software Foundation, Inc.
+# Copyright (C) 2004, 2005, 2006, 2007, 2008 Free Software
+# Foundation, Inc.
# Written by Gary V. Vaughan, 2004
#
# This file is part of GNU Libtool.
@@ -187,6 +188,8 @@
m4_define([LT_AT_TAG],
[AT_KEYWORDS([$1])
AT_CHECK([{ test -n [$]$1 test X[$]$1 != Xno; } || (exit 77)])
+m4_if([$1], [CXX],
+ [AT_CHECK([test X$CXX != Xg++ || (g++ -v /dev/null 21) || (exit 77)])])
])
Re: multilib patch
Hi Peter, * Peter O'Gorman wrote on Thu, Jan 31, 2008 at 08:00:59AM CET: I installed amd64 debian in a VM and with this patch I get: /usr/lib/gcc/x86_64-linux/gnu/4.1.2 /usr/lib /lib I do not know if it is best to leave in the symlink and the original dir ( i.e. do cd $dir pwd as well as cd $dir pwd -P), which on debian would give something like: /usr/lib/gcc/x86_64-linux/gnu/4.1.2 /usr/lib64 /usr/lib /lib64 /lib With this patch I get for -m32: sys_lib_search_path_spec=/usr/lib/gcc/x86_64-linux-gnu/4.0.3/../../.. /usr/lib/gcc/x86_64-linux-gnu/4.0.3/32 /usr/lib/gcc/x86_64-linux-gnu/4.0.3 /usr/lib32 /lib32 The first entry is wrong, as it's equal to /usr/lib which is 64bit. For -m64 I get: sys_lib_search_path_spec=/usr/lib/gcc/x86_64-linux-gnu/4.0.3 /usr/lib /lib I have not yet tried to understand the logic of the patch. Cheers, Ralf
Re: multilib patch
Ralf Wildenhues wrote: I have not yet tried to understand the logic of the patch. Sorry. I have dropped it. libstdc++ should still be found because of the compiler_search_path changes. Peter -- Peter O'Gorman http://pogma.com
Re: GNU Libtool 2.1b released (alpha release)
Hi Bob, On 1 Feb 2008, at 15:25, Gary V. Vaughan wrote: Aha! I get the same error if I undo that patch in my GraphicsMagick working copy, run bootstrap with libtoolize (2.1b). I'll see if I can figure out why I get this: $ grep argz.lo Makefile ltdl_LTLIBOBJS = argz.lo Instead of this: $ grep argz.lo Makefile ltdl_LTLIBOBJS = ltdl/argz.lo Okay, I've figured it out. The new libtoolize figured out that you want a nonrecursive libltdl because your bootstrap script runs: libtoolize --verbose --copy --force --nonrecursive --ltdl=ltdl But at configure time, the expansion of this code which is required to set the lt_libojb_prefix that puts the ltdl/ in front of argz.lo can't tell that it is running in nonrecursive mode: # _LTDL_MODE_DISPATCH # --- m4_define([_LTDL_MODE_DISPATCH], [dnl If _LTDL_DIR is `.', then we are configuring libltdl itself: m4_if(_LTDL_DIR, [], [], dnl if _LTDL_MODE was not set already, the default value is `subproject': [m4_case(m4_default(_LTDL_MODE, [subproject]), [subproject], [AC_CONFIG_SUBDIRS(_LTDL_DIR) _LT_SHELL_INIT([lt_dlopen_dir=$lt_ltdl_dir])], [nonrecursive], [_LT_SHELL_INIT([lt_dlopen_dir=$lt_ltdl_dir; lt_libobj_prefix=$lt_ltdl_dir/])], [recursive], [], [m4_fatal([unknown libltdl mode: ]_LTDL_MODE)])])dnl dnl Be careful not to expand twice: m4_define([$0], []) ])# _LTDL_MODE_DISPATCH And that's because the 2.1b interface is to declare the libltdl mode as an argument to LTDL_INIT. For quite a while the CVS builds required that the libltdl mode be declared as a second argument to LT_CONFIG_LTDL_DIR as you have in your unpatched configure.ac. The documentation reflects the state of the 2.1b release. So, in effect, the patch I attached to my last message is the correct fix for the error you were seeing. Do you think we should put undocumented support for the temporary interface we had for a while back in for the next alpha? (a serious question) Cheers, Gary -- ())_. Email me: [EMAIL PROTECTED] ( '/ Read my blog: http://blog.azazil.net / )= ...and my book: http://sources.redhat.com/autobook `(_~)_ PGP.sig Description: This is a digitally signed message part ___ http://lists.gnu.org/mailman/listinfo/libtool
[libtool 2.1b] testsuite: 16 54 55 56 failed
16. convenience.at:69: testing ...
./convenience.at:70: { test -n $CXX test X$CXX != Xno; } || (exit 77)
libtool: compile: g++ -c main1.cpp -o .libs/main1.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: compile: g++ -c a1.cpp -o .libs/a1.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: link: `a1.lo' is not a valid libtool object
libtool: compile: g++ -c main2.cpp -o .libs/main2.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: compile: g++ -c a2.cpp -o .libs/a2.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: link: `a2.lo' is not a valid libtool object
libtool: compile: g++ -c main3.cpp -o .libs/main3.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: compile: g++ -c a3.cpp -o .libs/a3.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: link: `a3.lo' is not a valid libtool object
./convenience.at:91: $LIBTOOL --tag=CXX --mode=link $CXX $CXXFLAGS $LDFLAGS -o
liba12.la liba1.la liba2.la -rpath /notexist
stderr:
libtool: link: cannot find the library `liba1.la' or unhandled argument
`liba1.la'
stdout:
./convenience.at:91: exit code was 1, expected 0
16. convenience.at:69: 16. C++ convenience archives (convenience.at:69): FAILED
(convenience.at:91)
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
___
Bug-libtool mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
Gary V. Vaughan [EMAIL PROTECTED] writes: Do you have a C++ compiler installed? No. What did configure report in the 'checking for g++' test? checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl.exe... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking dependency style of g++... none Did you have CXX set in your environment when you ran configure? No. I cannot answer the other questions ATM, because all I have is the build log. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And now for something completely different. ___ Bug-libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
Hallo Andreas,
Thanks for the report.
What architecture is this building on?
On 1 Feb 2008, at 22:43, Andreas Schwab wrote:
16. convenience.at:69: testing ...
./convenience.at:70: { test -n $CXX test X$CXX != Xno; } ||
(exit 77)
So CXX is a non-zero length string other than no, or this test would
have
skipped (exit code 77).
libtool: compile: g++ -c main1.cpp -o .libs/main1.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command
not found
It seems you have CXX=g++, but with no g++ in your path when you run
the testsuite.
What is CXX set to in your Makefile?
Do you have a C++ compiler installed?
Is it g++?
What did configure report in the 'checking for g++' test?
Did configure add a CXX tag to the libtool script (search for 'TAG
CONFIG: CXX'
in libtool in your build directory)?
What does the first CC= line below that say?
Did you have CXX set in your environment when you ran configure?
Cheers,
Gary
--
())_. Email me: [EMAIL PROTECTED]
( '/ Read my blog: http://blog.azazil.net
/ )= ...and my book: http://sources.redhat.com/autobook
`(_~)_
PGP.sig
Description: This is a digitally signed message part
___
Bug-libtool mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: GNU Libtool 2.1b released (alpha release)
On Fri, 1 Feb 2008, Gary V. Vaughan wrote: So, in effect, the patch I attached to my last message is the correct fix for the error you were seeing. Your micro-patch does work and does not bother me. Do you think we should put undocumented support for the temporary interface we had for a while back in for the next alpha? (a serious question) As long as package developers are aware of how things should be done in order to use latest libtool 2.1, it does not bother me if their packages do break. Libtool 2.1 is a work in progress and should be released soon. Other opinions may differ. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: GNU Libtool 2.1b released (alpha release)
Gary, It turns out that your micro-patch does not actually work since there is a failure during 'make distcheck': gmake[2]: *** No rule to make target `ltdl/argz.lo', needed by `ltdl/libltdlc.la'. Stop. gmake[2]: Leaving directory `/scratch/bfriesen/build/GraphicsMagick-16-static/GraphicsMagick-1.2.020080201/_build' This was working not very long ago ... Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
On Fri, 1 Feb 2008, Andreas Schwab wrote: Gary V. Vaughan [EMAIL PROTECTED] writes: Do you have a C++ compiler installed? No. I have a similar situation with Fortran since I have no other use for a Fortran compiler. In order to make the tests happy, I set both F77 and FC to 'no' in my /usr/local/share/config.site file. Presumably you could do the same for CXX. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ Bug-libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
On Sat, 2 Feb 2008, Gary V. Vaughan wrote: DTRT. There should be no need to tweak config.site for CXX if F77 and FC are handled transparently... It would be nice if F77 and FC were properly handled transparently. Make it so! :-) It seems that in Andreas's environment 'g++' appears out of thin air. In my own environment there is confusion because even though GCC is being used, configure tries to use the Sun fortran compilers (also installed) with GCC-style formulas so tests fail. It seems likely that Sun fortran compilers could successfully be used but there is an implicit assumption that if the C compiler is GCC that all tools will be from the same tool chain. Bob == Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ Bug-libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-libtool
GNU Libtool 1.5.26 released.
The Libtool Team is pleased to announce the release of GNU Libtool 1.5.26. GNU Libtool hides the complexity of using shared libraries behind a consistent, portable interface. GNU Libtool ships with GNU libltdl, which hides the comlexity of loading dynamic runtime libraries (modules) behind a consistent, portable interface. New in 1.5.26: February 1 2008 * Improved support for Mac OS X Leopard. * More robust parsing of mangled `.la' files inside libltdl, fixing a possible overrun and a crash due to memory exhaustion. * Fix compile command line for gcj on MinGW. * Some configure variables have been renamed to fix caching: lt_prog_compiler_pic_works to lt_cv_prog_compiler_pic_works lt_prog_compiler_static_works to lt_cv_prog_compiler_static_works. * Support for AIX 6.1. * Bug Fixes. libtool-1.5.26 is available now from ftp.gnu.org, along with diffs and xdeltas against libtool-1.5.24 that are also available from ftp.gnu.org. Please use a mirror to reduce stress on the main gnu machine: http://www.gnu.org/order/ftp.html Here are the compressed sources: ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.26.tar.gz Here are the xdeltas and diffs against libtool-1.5.24: ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.24-1.5.26.diff.gz ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.24-1.5.26.xdelta Here are the gpg detached signatures: ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.26.tar.gz.sig ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.24-1.5.26.diff.gz.sig ftp://ftp.gnu.org/gnu/libtool/libtool-1.5.24-1.5.26.xdelta.sig Here are the MD5 and SHA1 checksums: aa9c5107f3ec9ef4200eb6556f3b3c29 libtool-1.5.26.tar.gz 5b339d2aef3c0a92444507f2103b0ca4 libtool-1.5.24-1.5.26.diff.gz 3ea264200b77ce92654d0e704e1d1f1b libtool-1.5.24-1.5.26.xdelta 4c1738351736562a951a345e24f233d00953ec0a libtool-1.5.26.tar.gz 17110100a3a5925690b1e29c4168dc58efeacac8 libtool-1.5.24-1.5.26.diff.gz 0ca4a25a94390d994ec1477d439df56ab391b52e libtool-1.5.24-1.5.26.xdelta This release was bootstrapped with automake-1.10.1, autoconf-2.61 and m4-1.4.10, but is useable with older versions in your own projects. Alternatively, you can fetch the unbootstrapped sourcecode from anonymous cvs by using the following commands (just hit return when you are prompted for the password): $ export CVS_RSH=ssh $ cvs -z3 -d :pserver:[EMAIL PROTECTED]:/sources/libtool \ co -r release-1-5-26 libtool You will then need to have recent versions of Automake and Autoconf installed to bootstrap the checked out sources yourself. Please report bugs to [EMAIL PROTECTED]. -- Peter O'Gorman http://pogma.com ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
On 2 Feb 2008, at 01:02, Bob Friesenhahn wrote: On Fri, 1 Feb 2008, Andreas Schwab wrote: Gary V. Vaughan [EMAIL PROTECTED] writes: Do you have a C++ compiler installed? No. I have a similar situation with Fortran since I have no other use for a Fortran compiler. In order to make the tests happy, I set both F77 and FC to 'no' in my /usr/local/share/config.site file. Presumably you could do the same for CXX. I jumped through some hoops to build an f77 that match Apple's gcc installation under Panther, just so that I didn't have issues with libtool. For the last 2 years or so with Tiger and Leopard I have neither had a fortran compiler installed, or had to do anything special to make libtool DTRT. There should be no need to tweak config.site for CXX if F77 and FC are handled transparently... Cheers, Gary -- Gary V. Vaughan ([EMAIL PROTECTED]) PGP.sig Description: This is a digitally signed message part ___ Bug-libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: GNU Libtool 2.1b released (alpha release)
On 2 Feb 2008, at 01:21, Bob Friesenhahn wrote: Gary, Hi Bob! It turns out that your micro-patch does not actually work since there is a failure during 'make distcheck': gmake[2]: *** No rule to make target `ltdl/argz.lo', needed by `ltdl/ libltdlc.la'. Stop. gmake[2]: Leaving directory `/scratch/bfriesen/build/ GraphicsMagick-16-static/GraphicsMagick-1.2.020080201/_build' This was working not very long ago ... Yep, this is a real bug in 2.1b when running make distcheck with nonrecursive libltdl. Nice catch. Patch to follow... Cheers, Gary -- ())_. Email me: [EMAIL PROTECTED] ( '/ Read my blog: http://blog.azazil.net / )= ...and my book: http://sources.redhat.com/autobook `(_~)_ PGP.sig Description: This is a digitally signed message part ___ http://lists.gnu.org/mailman/listinfo/libtool
web page updates
I have updated the web pages to the new style, please let me know about typos etc. (or just fix them if you have commit :-p). Thanks, Peter -- Peter O'Gorman http://pogma.com ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
Bob Friesenhahn [EMAIL PROTECTED] writes: On Fri, 1 Feb 2008, Andreas Schwab wrote: Gary V. Vaughan [EMAIL PROTECTED] writes: Do you have a C++ compiler installed? No. I have a similar situation with Fortran since I have no other use for a Fortran compiler. In order to make the tests happy, I set both F77 and FC to 'no' in my /usr/local/share/config.site file. Presumably you could do the same for CXX. There is no problem with the missing fortran compiler. It looks like an autoconf bug: if no C++ compiler is found it uses g++ regardless. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 And now for something completely different. ___ Bug-libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: [libtool 2.1b] testsuite: 16 54 55 56 failed
Hello Andreas,
* Andreas Schwab wrote on Fri, Feb 01, 2008 at 03:43:25PM CET:
16. convenience.at:69: testing ...
./convenience.at:70: { test -n $CXX test X$CXX != Xno; } || (exit 77)
libtool: compile: g++ -c main1.cpp -o .libs/main1.o
/usr/src/packages/BUILD/libtool-2.1b/libtool: line 821: g++: command not found
libtool: compile: g++ -c a1.cpp -o .libs/a1.o
Thanks for the bug report. Fixed as follows.
The fact that AC_PROG_CXX sets CXX to g++ as a default seems to me like
a bug in Autoconf. The code used gcc as a default up to commit
d9409a1c3c06a015a0fc829989cb1a93c1599cd7
which it had ever since AC_PROG_CXX was added 1994 in commit
8202df5faf642cde4e5b1fa02cd9cc4411a7a477
I'll propose to remove that in Autoconf.
Cheers,
Ralf
2008-02-01 Ralf Wildenhues [EMAIL PROTECTED]
* tests/testsuite.at (LT_AT_TAG): For the CXX tag, if $CXX is
g++, check that `g++ -v' works; AC_PROG_CXX may have set that
as default value even if it found no C++ compiler.
Report by Andreas Schwab.
Index: tests/testsuite.at
===
RCS file: /cvsroot/libtool/libtool/tests/testsuite.at,v
retrieving revision 1.50
diff -u -r1.50 testsuite.at
--- tests/testsuite.at 25 Mar 2007 12:12:43 - 1.50
+++ tests/testsuite.at 1 Feb 2008 19:05:24 -
@@ -1,6 +1,7 @@
# Process with autom4te to create an -*- Autotest -*- test suite.
#
-# Copyright (C) 2004, 2005, 2006, 2007 Free Software Foundation, Inc.
+# Copyright (C) 2004, 2005, 2006, 2007, 2008 Free Software
+# Foundation, Inc.
# Written by Gary V. Vaughan, 2004
#
# This file is part of GNU Libtool.
@@ -187,6 +188,8 @@
m4_define([LT_AT_TAG],
[AT_KEYWORDS([$1])
AT_CHECK([{ test -n [$]$1 test X[$]$1 != Xno; } || (exit 77)])
+m4_if([$1], [CXX],
+ [AT_CHECK([test X$CXX != Xg++ || (g++ -v /dev/null 21) || (exit 77)])])
])
___
Bug-libtool mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/bug-libtool
Re: GNU Libtool 2.1b released (alpha release)
Hi Gary, * Gary V. Vaughan wrote on Fri, Feb 01, 2008 at 01:11:59PM CET: So, in effect, the patch I attached to my last message is the correct fix for the error you were seeing. Confirmed. Thanks for analysing this, and thanks also for cutting the release! Do you think we should put undocumented support for the temporary interface we had for a while back in for the next alpha? (a serious question) FWIW, I see no particular need to invest much time in this, either. Cheers, Ralf ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: web page updates
Hi Peter, * Peter O'Gorman wrote on Fri, Feb 01, 2008 at 07:54:54PM CET: I have updated the web pages to the new style, please let me know about typos etc. (or just fix them if you have commit :-p). I fixed a typo, committed the html_node pages, and added a manual/.symlinks file to resolve the links to other manuals. Cheers, Ralf ___ http://lists.gnu.org/mailman/listinfo/libtool
