Re: GNU Libtool 2.1b released (alpha release)

fdec-mozilla are fine with libtool CVS trunk. Even "make distcheck" passes. x86_64, Fedora 8 with all updates. No exotic unices, sorry. -- Regards, Pavel Roskin ___ http://lists.gnu.org/mailman/listinfo/libtool

pkg-config and versioning of static libraries

t I could not find anything that would explain position of the libtool developers in this question. I don't want to add libtool support for GNU Midnight Commander just because it's linked against glib. If you think it's a good idea, I'd like to hear arguments. -- Regards, Pavel Roskin ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

Re: Libtool 1.4.3

they are better tested when used together. There may be technical reasons to require latest Autoconf as well, but they are secondary IMHO. > I'll probably be flamed to hell and back now... Not in this list. -- Regards, Pavel Roskin ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

Re: Libtool 1.4.3

e more portable. If libtool 1.4.3 is going to provide compatibility with MacOS (i.e. zsh, if I understand correctly), then it's absolutely reasonable to require the developer to spend some time and make sure that the configure script provides the same level of compatibility. -- Regards, Pavel

Re: [ 100058 ] 1.4 - $buildir-path may not contain "~"

lt_cv_path_MAGIC_CMD="$ac_dir/$1" @@ -3420,6 +3427,7 @@ [if test -z "$LD"; then IFS="${IFS= }"; ac_save_ifs="$IFS"; IFS="${IFS}${PATH_SEPARATOR-:}" for ac_dir in $PATH; do +IFS="$ac_save_ifs" test -z "$ac_dir" && ac_dir=. if test -f "$ac_dir/$ac_prog" || test -f "$ac_dir/$ac_prog$ac_exeext"; then lt_cv_path_LD="$ac_dir/$ac_prog" @@ -3665,6 +3673,7 @@ else IFS="${IFS= }"; ac_save_ifs="$IFS"; IFS="${IFS}${PATH_SEPARATOR-:}" for ac_dir in $PATH /usr/ccs/bin /usr/ucb /bin; do +IFS="$ac_save_ifs" test -z "$ac_dir" && ac_dir=. tmp_nm=$ac_dir/${ac_tool_prefix}nm if test -f $tmp_nm || test -f $tmp_nm$ac_exeext ; then Regards, Pavel Roskin ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

CVS problems

cvs server: failed to create lock directory in repository `/cvs/libtool/CVSROOT': Permission denied cvs server: failed to obtain dir lock in repository `/cvs/libtool/CVSROOT' cvs [server aborted]: read lock failed - giving up I'm using CVS 1.11.0.1. Regard

Re: Forbidden strings

ure:5870: error: undefined macro: lt_AR_FLAGS > configure:5870: error: undefined macro: AR_FLAGS > > What should we do? Return to A[CHMSTU] Regards, Pavel Roskin ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

Re: mulit-language-branch BUG: circular macro dependencies

he dependencies, but I didn't > see one. Could someone comment on what happened? I'm afraid that you are trying to find a problem on the top level that actully sits in the subdirs. Regards, Pavel Roskin ___ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool

Re: [Autoconf] Re: Libtool warning message

_LANG_C in AC_LIBTOOL_SETUP, which _probably_ means that running ltconfig in the C++ mode is not ruled out. Otherwise, you need a check in ltconfig.in that the current language is C and nothing else. You may also need to use AC_LANG_C not only for "sco3.2v5" Regards, Pavel Roskin

Re: changequote used incorrectly

ot; looks in /usr/info before the current directory. Not very intuitive :-( > So in the case Pavel fixed, I'd suggest to follow the advice of Lars. I'm fixed now :-) I'll try to remove changequote()s from libtool.m4 as long as it remains compatible with Autoconf-2.13 Regards, Pavel Roskin

changequote used incorrectly

08:22:46 2000 +++ ChangeLog Thu Sep 7 13:36:19 2000 @@ -0,0 +1,5 @@ +2000-09-07 Pavel Roskin <[EMAIL PROTECTED]> + + * libtool.m4 (_LT_AC_LTCONFIG_HACK): fixed incorrect use of + changequote + Index: libtool.m4 --- libtool.m4 Thu Sep 7 13:30:38 2000 +++ libtool.m4 Thu Sep 7

Something bad happened

d not be backslashed in: [[configure: WARNING: [\`$CC' requires \`$ac_cv_prog_cc_shlib' to build shared libraries]]] ]configure.in:8: /usr/bin/m4: Non-numeric argument to built-in `m4exit' I haven't investigated the problem in depth. It must be an incomplete commit or something like that. I hope you will fix this promptly. Regards, Pavel Roskin

Re: Ensuring compatibility between libtool components

code to "configure". I believe that you will have to fool either aclocal or autoconf, so my opinion will depend on how you are going to do it. Regards, Pavel Roskin

Re: ultrix, cache_file and ksh

nks for your > help. Maybe this patch will save time to somebody with write access to the repository: Index: ChangeLog --- ChangeLog Mon Jul 24 08:50:46 2000 +++ ChangeLog Fri Jul 28 14:00:13 2000 @@ -0,0 +1,4 @@ +2000-07-28 Pavel Roskin <[EMAIL PROTECT

Re: ultrix, cache_file and ksh

f" is used to check whether the file is regular or not. > if test -n "$cache_file" && test -r "$cache_file"; then This should become if test -n "$cache_file" && test -r "$cache_file" && test -f \ "$cache_file"; then Please check that it works for your ksh. Regards, Pavel Roskin

Extra 'g' in libltdl/ltdl.c

Hello! The CVS/Head version of libltdl/ltdl.c begins with 'g' Please be careful and run "make check" before "cvs commit" Time to setup Tinderbox for Auto* tools? Regards, Pavel Roskin

Target for libtool?

" ;; esac This change passes "make check" in libtool (provided that a typo in libltdl/ltdl.c if fixed as well) Just in case, I'm using RedHat Linux 6.1 on i586 with gcc-2.95.2, bash-1.14.7, m4-1.4, CVS/Head verions of Autoconf, Automake and Libtool. Regards, Pavel Roskin

Re: AC_CANONICAL_BUILD

nf. Current CVS versions of libtool, autoconf and automake work together again. You may want to use "make check" to make sure that they actually work. Pavel Roskin

bug in libltdl/ltdl.c (fwd)

Hello! This should certainly go to [EMAIL PROTECTED] Pavel Roskin -- Forwarded message -- Date: Wed, 23 Feb 2000 15:55:40 -0700 From: Patrick Tullmann <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: Kaffe <[EMAIL PROTECTED]> Subject: bug in libltdl/ltdl.c Rese

Re: file_magic broken

Hello, Gary! It's finally fixed. Tested on LinuxPPC. Thank you! Pavel

Re: file_magic broken

IC variable%%%" make still hangs in libltdl both on LinuxPPC and Linux-i386 (after removing "i*86 |" from libtool.m4) MAGIC is defined in many makefiles (Makefile.in, tests/Makefile.in, doc/Makefile.in) but not in libltdl/Makefile.in PS. The same problem can be reproduced with automake-1.4-19980208 (from LinuxPPC) and autoconf-2.13 Cheers, Pavel Roskin

file_magic broken

k gcc -g -O2 -o libltdl.la -rpath /usr/local/lib -no-undefined -version-info 2:0:2 ltdl.lo -ldl rm -fr .libs/libltdl.la .libs/libltdl.* .libs/libltdl.* It appears that $FILE is defined to an empty string. It's output is fed to sed or egrep, and they expect input on stdin. Regards, Pavel Roskin

Test case for the problem in Kaffe

lback() * mdemo/foo1.c (hello): call test_callback * mdemo/foo2.c (hello): Likewise As you can see, mdemo.static cannot be linkled anymore. There is no fix yet. Hopefully people more experiences in dlopen() matters can do it better/faster. Pavel Roskin mdemo.diff.gz