libtool ChangeLog tests/lt_dlexit.at
CVSROOT:/cvsroot/libtool Module name:libtool Changes by: Ralf Wildenhues rwild 07/01/29 21:59:59 Modified files: . : ChangeLog tests : lt_dlexit.at Log message: * tests/lt_dlexit.at: Use $abs_top_srcdir, not $top_srcdir, in the new testsuite. CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/libtool/ChangeLog?cvsroot=libtoolr1=1.2372r2=1.2373 http://cvs.savannah.gnu.org/viewcvs/libtool/tests/lt_dlexit.at?cvsroot=libtoolr1=1.1r2=1.2 ___ Libtool-commit mailing list Libtool-commit@gnu.org http://lists.gnu.org/mailman/listinfo/libtool-commit
Re: (no subject)
On Jan 23, 2007, at 8:05 AM, Brian W. Barrett wrote: Hi - I think I've stumbled on a bug in the libtool 2 snapshots (in particular, last night's snapshot) when building 64 bit builds on OS X. I've run into this when building Open MPI, but I think it could happen on any project that had internal library dependencies. Builds will fail with the error message below the first time something tries to link against a shared library that has a dependency on another shared library (in this case, the errmgr_hnp component depends on libopen-rte, which depends on libopen-pal). I applied your patch as is with this changelog: 2007-01-29 Brian W. Barrett [EMAIL PROTECTED] * libltdl/config/ltmain.m4sh [darwin]: Use otool64 if otool fails. Thanks, Peter
Re: silence m4 --warn-syntax warning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 1/29/2007 6:53 AM:
Using /usr/local/bin/m4 as a wrapper around CVS branch-1_4 of M4 (ie. the
eventual M4 1.4.9), I got this false positive:
/home/eblake/m4/build/src/m4:ltdl/m4/libtool.m4:916: Warning: semantics of
`${1...}' in defn of `_LT_PROG_ECHO_BACKSLASH' will change
autom4te: /usr/local/bin/m4 failed with exit status: 1
OK to apply this patch?
The first cut wasn't big enough. Note that this patch is not strictly
necessary if autoconf disables ${} parsing in M4 altogether; it only
silences false positives from masochistic users that try out the new m4
- --warn-syntax option in spite of the warning in M4's documentation that
the option is not compatible with autoconf 2.61.
How about this instead:
2007-01-29 Eric Blake [EMAIL PROTECTED]
* libltdl/m4/libtool.m4 (_LT_PROG_ECHO_BACKSLASH): Avoid issues
with m4-1.4.9 --warn-syntax.
(_LT_PROG_XSI_SHELLFNS): Likewise.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFvf+H84KuGfSFAYARAvIEAKCBNtwSFmHJXx5K75qQZd5h2rurGQCdEs9V
00cID4TKZM6ghFbZCcYxHq4=
=Ir29
-END PGP SIGNATURE-
? libltdl/config/libtoolize
Index: libltdl/m4/libtool.m4
===
RCS file: /sources/libtool/libtool/libltdl/m4/libtool.m4,v
retrieving revision 1.88
diff -u -p -r1.88 libtool.m4
--- libltdl/m4/libtool.m4 28 Jan 2007 13:03:47 - 1.88
+++ libltdl/m4/libtool.m4 29 Jan 2007 14:06:01 -
@@ -937,7 +937,7 @@ elif test X`{ $ECHO '\t'; } 2/dev/null
:
else
# Restart under the correct shell.
- exec $SHELL [$]0 --no-reexec ${1+[$]@}
+ exec $SHELL [$]0 --no-reexec [$]{1+[$]@}
fi
if test X[$]1 = X--fallback-echo; then
@@ -1004,7 +1004,7 @@ if test -z $lt_ECHO; then
export ORIGINAL_CONFIG_SHELL
CONFIG_SHELL=/bin/ksh
export CONFIG_SHELL
-exec $CONFIG_SHELL [$]0 --no-reexec ${1+[$]@}
+exec $CONFIG_SHELL [$]0 --no-reexec [$]{1+[$]@}
else
# Try using printf.
ECHO='printf %s\n'
@@ -1042,7 +1042,7 @@ if test -z $lt_ECHO; then
if test $prev != 'sed 50q [$]0'; then
echo_test_string=`eval $prev`
export echo_test_string
- exec ${ORIGINAL_CONFIG_SHELL-${CONFIG_SHELL-/bin/sh}} [$]0
${1+[$]@}
+ exec ${ORIGINAL_CONFIG_SHELL-${CONFIG_SHELL-/bin/sh}} [$]0
[$]{1+[$]@}
else
# Oops. We lost completely, so just stick with echo.
ECHO=echo
@@ -2129,7 +2129,7 @@ darwin* | rhapsody*)
shlibpath_var=DYLD_LIBRARY_PATH
shrext_cmds='`test .$module = .yes echo .so || echo .dylib`'
m4_if([$1], [],[
- sys_lib_search_path_spec=$sys_lib_search_path_spec /usr/local/lib])
+ sys_lib_search_path_spec=$sys_lib_search_path_spec /usr/local/lib])
sys_lib_dlsearch_path_spec='/usr/local/lib /lib /usr/lib'
;;
@@ -2310,7 +2310,7 @@ linux* | k*bsd*-gnu)
finish_cmds='PATH=\$PATH:/sbin ldconfig -n $libdir'
shlibpath_var=LD_LIBRARY_PATH
shlibpath_overrides_runpath=no
- # Some binutils ld are patched to set DT_RUNPATH
+ # Some binutils ld are patched to set DT_RUNPATH
save_LDFLAGS=$LDFLAGS
save_libdir=$libdir
eval libdir=/foo wl=$_LT_TAGVAR(lt_prog_compiler_wl, $1) \
@@ -7012,16 +7012,16 @@ m4_defun([_LT_PROG_XSI_SHELLFNS],
# otherwise set result to NONDIR_REPLACEMENT.
func_dirname ()
{
- case ${1} in
-*/*) func_dirname_result=${1%/*}${2} ;;
-* ) func_dirname_result=${3} ;;
+ case [$]{1} in
+*/*) func_dirname_result=[$]{1%/*}[$]{2} ;;
+* ) func_dirname_result=[$]{3} ;;
esac
}
# func_basename file
func_basename ()
{
- func_basename_result=${1##*/}
+ func_basename_result=[$]{1##*/}
}
# func_stripname prefix suffix name
@@ -7033,9 +7033,9 @@ func_stripname ()
{
# pdksh 5.2.14 does not do ${X%$Y} correctly if both X and Y are
# positional parameters, so assign one to ordinary parameter first.
- func_stripname_result=${3}
- func_stripname_result=${func_stripname_result#${1}}
- func_stripname_result=${func_stripname_result%${2}}
+ func_stripname_result=[$]{3}
+ func_stripname_result=${func_stripname_result#[$]{1}}
+ func_stripname_result=${func_stripname_result%[$]{2}}
}
_LT_EOF
;;
@@ -7047,18 +7047,18 @@ _LT_EOF
func_dirname ()
{
# Extract subdirectory from the argument.
- func_dirname_result=`$ECHO X${1} | $Xsed -e $dirname`
- if test X$func_dirname_result = X${1}; then
-func_dirname_result=${3}
+ func_dirname_result=`$ECHO X[$]{1} | $Xsed -e $dirname`
+ if test X$func_dirname_result = X[$]{1}; then
+func_dirname_result=[$]{3}
else
-func_dirname_result=$func_dirname_result${2}
+
Re: silence m4 --warn-syntax warning
Hello Eric,
Thanks for your work.
* Eric Blake wrote on Mon, Jan 29, 2007 at 03:07:04PM CET:
2007-01-29 Eric Blake [EMAIL PROTECTED]
* libltdl/m4/libtool.m4 (_LT_PROG_ECHO_BACKSLASH): Avoid issues
with m4-1.4.9 --warn-syntax.
(_LT_PROG_XSI_SHELLFNS): Likewise.
Extra bonus if you port to branch-1-5 as well, and if you kill all
now-superfluous curly braces that were only introduced to keep M4
away. For example, this:
- case ${1} in
-*/*) func_dirname_result=${1%/*}${2} ;;
-* ) func_dirname_result=${3} ;;
+ case [$]{1} in
+*/*) func_dirname_result=[$]{1%/*}[$]{2} ;;
+* ) func_dirname_result=[$]{3} ;;
can be simplified to this:
case [$]1 in
*/*) func_dirname_result=[$]{1%/*}[$]2 ;;
* ) func_dirname_result=[$]3 ;;
but also I'd prefer to follow `(autoconf.info)Coding Style' and then
write this:
case $[1] in
*/*) func_dirname_result=[$]{1%/*}$[2] ;;
* ) func_dirname_result=$[3] ;;
Ahh. See how the coding style now comes out inconsistent?
So let's go back there and address that first, before we do
anything about Libtool. (Continued in the respective thread
on autoconf-patches.)
Cheers,
Ralf
Re: Bug#407079: libtool: All GNU targets support -Wl, --version-script
[ Libtoolers, this is http://bugs.debian.org/407079 ]
* Samuel Thibault wrote on Tue, Jan 23, 2007 at 01:43:36AM CET:
Michael Banck, le Mon 22 Jan 2007 22:38:49 +0100, a écrit :
Hopefully somebody can check that on CVS HEAD, do you expect big problems?
[ ...make check and ]
make check-local got all success except:
18: shlibpath_overrides_runpath FAILED (shlibpath.at:61)
That's good enough for me.
That may not be a bug in libtool, though.
Probably is. I'll put it on the list of things to debug with
more time at hand...
I'm checking this in on branch-1-5 and HEAD, respectively.
No, I'm not moving the whole block to ensure sorted entries.
That can still be done when we've moved away from CVS
(which in turn I won't agree to before the 2.0 release).
Cheers,
Ralf
2007-01-29 Samuel Thibault [EMAIL PROTECTED]
* libltdl/m4/libtool.m4 (_LT_LINKER_SHLIBS) [ gnu ]
archive_expsym_cmds: Behave like Linux, so that
--version-script is used for Hurd as well.
Index: libltdl/m4/libtool.m4
===
RCS file: /cvsroot/libtool/libtool/libltdl/m4/libtool.m4,v
retrieving revision 1.88
diff -u -r1.88 libtool.m4
--- libltdl/m4/libtool.m4 28 Jan 2007 13:03:47 - 1.88
+++ libltdl/m4/libtool.m4 29 Jan 2007 19:48:37 -
@@ -4163,7 +4163,7 @@
_LT_TAGVAR(archive_expsym_cmds, $1)='sed s,^,_, $export_symbols
$output_objdir/$soname.expsym~$CC -shared $pic_flag $libobjs $deplibs
$compiler_flags ${wl}-h,$soname
${wl}--retain-symbols-file,$output_objdir/$soname.expsym
${wl}--image-base,`expr ${RANDOM-$$} % 4096 / 2 \* 262144 + 1342177280` -o $lib'
;;
-linux* | tpf* | k*bsd*-gnu)
+gnu* | linux* | tpf* | k*bsd*-gnu)
tmp_diet=no
if test $host_os = linux-dietlibc; then
case $cc_basename in
2007-01-29 Samuel Thibault [EMAIL PROTECTED]
* libtool.m4 (AC_LIBTOOL_PROG_LD_SHLIBS) [ gnu ]
archive_expsym_cmds: Behave like Linux, so that
--version-script is used for Hurd as well.
Index: libtool.m4
===
RCS file: /cvsroot/libtool/libtool/Attic/libtool.m4,v
retrieving revision 1.314.2.168
diff -u -r1.314.2.168 libtool.m4
--- libtool.m4 28 Jan 2007 13:04:20 - 1.314.2.168
+++ libtool.m4 29 Jan 2007 19:49:11 -
@@ -5662,7 +5662,7 @@
_LT_AC_TAGVAR(archive_expsym_cmds, $1)='sed s,^,_, $export_symbols
$output_objdir/$soname.expsym~$CC -shared $pic_flag $libobjs $deplibs
$compiler_flags ${wl}-h,$soname
${wl}--retain-symbols-file,$output_objdir/$soname.expsym
${wl}--image-base,`expr ${RANDOM-$$} % 4096 / 2 \* 262144 + 1342177280` -o $lib'
;;
-linux* | k*bsd*-gnu)
+gnu* | linux* | k*bsd*-gnu)
if $LD --help 21 | grep ': supported targets:.* elf' /dev/null; then
tmp_addflag=
case $cc_basename,$host_cpu in
Re: [patch] Dangling Pointer in libltdl
* quoting myself again:
* tests/lt_dlexit.at: New test.
And the installed ltdl.h played tricks on me too.
Here's a fix for the CVS HEAD test.
Cheers,
Ralf
2007-01-29 Ralf Wildenhues [EMAIL PROTECTED]
* tests/lt_dlexit.at: Use $abs_top_srcdir, not $top_srcdir,
in the new testsuite.
Index: tests/lt_dlexit.at
===
RCS file: /cvsroot/libtool/libtool/tests/lt_dlexit.at,v
retrieving revision 1.1
diff -u -r1.1 lt_dlexit.at
--- tests/lt_dlexit.at 28 Jan 2007 14:55:01 - 1.1
+++ tests/lt_dlexit.at 29 Jan 2007 21:57:56 -
@@ -114,7 +114,7 @@
int vb1 = 3;
]])
-: ${LTDLINCL=-I$top_srcdir/libltdl}
+: ${LTDLINCL=-I$abs_top_srcdir/libltdl}
: ${LIBLTDL=$abs_builddir/../libltdl/libltdlc.la}
CPPFLAGS=$CPPFLAGS $LTDLINCL
Re: silence m4 --warn-syntax warning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 1/29/2007 11:43 AM:
Hello Eric,
Hello Ralf,
Extra bonus if you port to branch-1-5 as well, and if you kill all
now-superfluous curly braces that were only introduced to keep M4
away.
No problem...
but also I'd prefer to follow `(autoconf.info)Coding Style' and then
write this:
case $[1] in
*/*) func_dirname_result=[$]{1%/*}$[2] ;;
* ) func_dirname_result=$[3] ;;
Ahh. See how the coding style now comes out inconsistent?
...once we settle this on the autoconf list.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFvsKB84KuGfSFAYARAhowAKDB3s/pill7AnNhOdGZe7p5NudIkwCdHWFR
w//zqETu6dCwm0Oqvxcipik=
=z/ms
-END PGP SIGNATURE-
Re: Libtool LynxOS support
On Mon, 29 Jan 2007, Olli Savia wrote: Hi, Could somebody please add LynxOS support to libtool. LynxOS uses GNU toolchain so it shouldn't be too hard. On LynxOS only one additional parameter (-mshared) is needed when compiling and linking. As I recall (from long ago) under LynxOS, all libraries need to applied during linking a shared library, and the result is more like static libraries loaded into pre-assigned offsets (not run-time relocated). The address offsets for each library are computed at link time. Is that still the case with LynxOS? 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 LynxOS support
Hi, Bob Friesenhahn wrote: On Mon, 29 Jan 2007, Olli Savia wrote: Hi, Could somebody please add LynxOS support to libtool. LynxOS uses GNU toolchain so it shouldn't be too hard. On LynxOS only one additional parameter (-mshared) is needed when compiling and linking. As I recall (from long ago) under LynxOS, all libraries need to applied during linking a shared library, and the result is more like static libraries loaded into pre-assigned offsets (not run-time relocated). The address offsets for each library are computed at link time. Is that still the case with LynxOS? No. Since LynxOS 4.0 shared libs are properly supported. LynxOS can even use Linux shared libs and run Linux binaries. Regards, Olli ___ http://lists.gnu.org/mailman/listinfo/libtool
1.5 bootstrap problems
Some recent change to the 1.5 branch of libtool caused make to enter an infinite loop trying to generate config.status based on what I had lying around from previous incremental builds, and I gave up and just bootstrapped a clean checkout instead. In the process, I discovered that bootstrapping the branch is not 'make -j2' clean: Making all in . make[1]: Entering directory `/home/eblake/libtool-branch' rm -f ltmain.shT CONFIG_FILES=libtoolize CONFIG_HEADERS= /bin/sh ./config.status make[1]: *** No rule to make target `libltdl/ltmain.sh', needed by `all-am'. Stop. make[1]: *** Waiting for unfinished jobs date=`/bin/sh ./mkstamp ./ChangeLog` \ sed -e 's/@''PACKAGE@/libtool/' -e 's/@''VERSION@/1.5.23a/' \ -e s%@[EMAIL PROTECTED] ./ltmain.in ltmain.shT mv -f ltmain.shT ltmain.sh || \ (rm -f ltmain.sh cp ltmain.shT ltmain.sh rm -f ltmain.shT) cp ltmain.sh ./libltdl/ config.status: creating libtoolize config.status: executing depfiles commands chmod +x libtoolize make[1]: Leaving directory `/home/eblake/libtool-branch' make: *** [all-recursive] Error 1 -- Eric Blake ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: 1.5 bootstrap problems
Hi Eric, * Eric Blake wrote on Mon, Jan 29, 2007 at 04:53:53PM CET: Some recent change to the 1.5 branch of libtool caused make to enter an infinite loop trying to generate config.status based on what I had lying around from previous incremental builds, and I gave up and just bootstrapped a clean checkout instead. AFAIK this bug has been around for a long time, not just recently. I've gotten into the habit of touch config.status; make for branch-1-5 Libtool, which seems to work. Or just using a new build tree. I'm not ambitious enough to look into a fix; on HEAD, things should work better (and there I /would/ be inclined to fix issues).[1] In the process, I discovered that bootstrapping the branch is not 'make -j2' clean: Sure, granted. -j2 isn't going to gain you anything there, though, as there's virtually nothing to do in parallel. Again, on HEAD that should be working as well. Cheers, Ralf [1] Actually, I do know of a small race on HEAD, but I haven't analyzed it yet. It causes `libtool' to be rebuilt early after a `cvs update', then later the script fails its consistency check (between macro_revision and ltmain.sh version). ___ http://lists.gnu.org/mailman/listinfo/libtool
Re: no .so file on HPUX platform?
Ralf Wildenhues [EMAIL PROTECTED] writes: * Ed Hartnett wrote on Mon, Jan 22, 2007 at 09:31:36PM CET: I only have this one HPUX system to test on, and it's pretty out of date, I suspect. But if I ask them to upgrade it, they'll probably just say Nah, let's just get rid of it... Do you have aCC installed there? If yes, could you try to build netcdf with it? Over here it's chosen, rather than CC, as C++ compiler. OK, this gave me the clue to try with with CXX=g++. This allows libtool to continue to build shared libraries. But there is still a problem, alas! Can anyone tell me why this link is failing? /bin/sh ../libtool --tag=CC--mode=link cc -g -version-info 4:0:0 -no-undefined -o libnetcdf.la -rp\ ath /usr/local/lib attr.lo ncx.lo putget.lo dim.lo error.lo libvers.lo nc.lo string.lo v1hpg.lo var.lo posixio.l\ o libtool: link: cc -b -Wl,+h -Wl,libnetcdf.sl.4 -Wl,+b -Wl,/usr/local/lib -o .libs/libnetcdf.sl.4.0 .libs/attr.o .l\ ibs/ncx.o .libs/putget.o .libs/dim.o .libs/error.o .libs/libvers.o .libs/nc.o .libs/string.o .libs/v1hpg.o .libs/va\ r.o .libs/posixio.o -lc cc: warning 422: Unknown option b ignored. /usr/ccs/bin/ld: Unsatisfied symbols: main (Not referenced yet! Probably due to -u option) *** Error exit code 1 Stop. *** Error exit code 1 -- Ed Hartnett -- [EMAIL PROTECTED] ___ http://lists.gnu.org/mailman/listinfo/libtool
how to give dependency library in libtool on hpux PA
Hi , I am facing problem on giving dependency path through automake on hpux PA 32 bit . When i genreating shared library libsample2.sl which is dependent on libsample1.sl which genreated but not installed in the mcahine.so while generating libsample2.sl i have given the libfmkmgr_la_LIBADD ../../src/.libs/libsample1.la With this Iam able to generate the shared library libsample2.sl. but when i do chatr on the library, it shows dependend path as static for libssampl1.sl. This problem iam facing on HPUX 11.i PA 32 bit only. how to change the dependend path as dyanmic. please find the sample Makefile.am . lib_LTLIBRARIES = libsample2.la libfmkmgr_la_LIBADD ../../src/.libs/libsample1.la libsample2_la_SOURCES = *.c ---chatr output for libsample2.sl chatr libsample2.sl shared library shared library dynamic path search: SHLIB_PATH enabled second embedded path enabled first /opt/OC/lib internal name: libsample2.sl.0 shared library list: static../../src/.libs/libsample1.la Any suggestion / help will be appreciated. Thanks, Joseph. -- View this message in context: http://www.nabble.com/how-to-give-dependency-library-in-libtool-on-hpux-PA-tf3140847.html#a8704915 Sent from the Gnu - Libtool - Discuss mailing list archive at Nabble.com. ___ http://lists.gnu.org/mailman/listinfo/libtool
