Re: Running ranlib after installation - okay or not?

2005-09-01 Thread Ralf Wildenhues
Hi Peter, * Peter O'Gorman wrote on Thu, Sep 01, 2005 at 07:09:35AM CEST: Peter O'Gorman wrote: | The problem is that libtool tries to run ranlib after install and that | ranlib can fail if the library is not writable? Thanks for the pointer. When I look more closely at this, I see in

Re: Running ranlib after installation - okay or not?

2005-09-01 Thread Peter O'Gorman
Ralf Wildenhues wrote: Should that be: old_postinstall_cmds=$old_postinstall_cmds~\$RANLIB \$oldlib ?? Yes, I believe so (both CVS HEAD and branch-1-5). Unless there exists ranlib's that change file mode.. Okay, the attached pathces are applied to libtool HEAD and branch-1-5. Thank you,

libtool ChangeLog libtoolize.m4sh

2005-09-01 Thread Gary V . Vaughan
CVSROOT:/cvsroot/libtool Module name:libtool Branch: Changes by: Gary V. Vaughan [EMAIL PROTECTED] 05/09/01 11:13:24 Modified files: . : ChangeLog libtoolize.m4sh Log message: * libtoolize.m4sh (func_scan_files): When searching for

libtool ChangeLog bootstrap

2005-09-01 Thread Ralf Wildenhues
CVSROOT:/cvsroot/libtool Module name:libtool Branch: Changes by: Ralf Wildenhues [EMAIL PROTECTED] 05/09/01 14:15:29 Modified files: . : ChangeLog bootstrap Log message: * bootstrap: Do not use nonportable -path. Reported by Ralf

Re: fix libtoolize scan of non-m4_include style aclocal.m4 [libtool--gary--1.0--patch-38..39]

2005-09-01 Thread Ralf Wildenhues
Hi Gary, * Gary V. Vaughan wrote on Thu, Sep 01, 2005 at 03:45:03AM CEST: Okay to commit to HEAD? * libtoolize.m4sh (func_scan_files): When searching for evidence of Autotools in aclocal.m4, be careful not to trip over requires and defuns. It makes things better

Re: fix libtoolize scan of non-m4_include style aclocal.m4 [libtool--gary--1.0--patch-38..39]

2005-09-01 Thread Gary V. Vaughan
Hallo Ralf, Ralf Wildenhues wrote: * Gary V. Vaughan wrote on Thu, Sep 01, 2005 at 03:45:03AM CEST: Okay to commit to HEAD? * libtoolize.m4sh (func_scan_files): When searching for evidence of Autotools in aclocal.m4, be careful not to trip over requires and defuns.

Re: use --enable-pic [libtool--gary--1.0--patch-32]

2005-09-01 Thread Ralf Wildenhues
* Noah Misch wrote on Tue, Aug 30, 2005 at 07:26:14PM CEST: On Tue, Aug 30, 2005 at 12:30:35PM +0100, Gary V. Vaughan wrote: * libltdl/m4/options.m4 (_LT_WITH_PIC): Renamed... (_LT_ENABLE_PIC): ...this. Adjust all callers. The configure option is now `--enable-pic', since

Re: fix libtoolize scan of non-m4_include style aclocal.m4 [libtool--gary--1.0--patch-38..39]

2005-09-01 Thread Gary V. Vaughan
Ralf Wildenhues wrote: * Gary V. Vaughan wrote on Thu, Sep 01, 2005 at 11:09:31AM CEST: Ralf Wildenhues wrote: * Gary V. Vaughan wrote on Thu, Sep 01, 2005 at 03:45:03AM CEST: Okay to commit to HEAD? * libtoolize.m4sh (func_scan_files): When searching for evidence of Autotools in

FYI: HEAD: Kill two showstoppers at once

2005-09-01 Thread Ralf Wildenhues
Hi Gary, * Gary V. Vaughan wrote on Wed, Aug 31, 2005 at 02:45:32PM CEST: Ralf Wildenhues wrote: Ah, okay. We just need to move the _LT_SET_OPTIONS up the expansion stack. If it didn't take arguments we could just AC_REQUIRE a wrapper, Isn't that what the optional second argument to

HEAD: small fixes

2005-09-01 Thread Ralf Wildenhues
A couple of small issues: a) On Solaris, `find' does not understand non-POSIX option `-path'. I believe testing against -name '{arch}' should be safe, right? b) aclocal-1.8 of standalone libltdl fails with | aclocal: macro `_LT_PROG_CXX' required but not defined | aclocal: macro `_LT_PROG_F77'

Re: the ltdl issue(s)

2005-09-01 Thread Ralf Wildenhues
* Gary V. Vaughan wrote on Thu, Sep 01, 2005 at 03:34:26PM CEST: Patrick Welche wrote: On Thu, Aug 18, 2005 at 07:31:31PM +0200, Ralf Wildenhues wrote: I just tried to bootstrap a clean checkout of today's libtool cvs with current cvs autotools, and seem to encounter some of the issues

Re: HEAD: small fixes

2005-09-01 Thread Gary V. Vaughan
Ralf Wildenhues wrote: A couple of small issues: [[snip]] OK to apply them? * bootstrap: Do not use nonportable -path. Reported by Ralf Menzel [EMAIL PROTECTED]. Yep. Please commit! * libltdl/m4/libtool.m4 (_LT_PROG_CXX, _LT_PROG_F77) (_LT_PROG_FC):

FYI: HEAD: small fixes

2005-09-01 Thread Ralf Wildenhues
* Gary V. Vaughan wrote on Thu, Sep 01, 2005 at 04:06:02PM CEST: Ralf Wildenhues wrote: * bootstrap: Do not use nonportable -path. Reported by Ralf Menzel [EMAIL PROTECTED]. Yep. Please commit! * libltdl/m4/libtool.m4 (_LT_PROG_CXX, _LT_PROG_F77)

Re: Running ranlib after installation - okay or not?

2005-09-01 Thread Peter O'Gorman
Ralf Wildenhues wrote: Should that be: old_postinstall_cmds=$old_postinstall_cmds~\$RANLIB \$oldlib ?? Yes, I believe so (both CVS HEAD and branch-1-5). Unless there exists ranlib's that change file mode.. Okay, the attached pathces are applied to libtool HEAD and branch-1-5. Thank you,

Re: the ltdl issue(s)

2005-09-01 Thread Patrick Welche
On Thu, Sep 01, 2005 at 03:51:08PM +0200, Ralf Wildenhues wrote: Even better: MAKE=gmake /bin/sh -vx ./bootstrap You know my setup too well ;-) One with a broken `make', and a `find' without `-path', I guess. The rest should be followup failures. My find claims to have -path, but I also

Re: how to link with installed libltdl?

2005-09-01 Thread Andreas Jellinghaus
Howard Chu wrote: In OpenLDAP's configure.in we use ... so does libltdl never need any libraries linked to it? like -ldl on some systems or something else? all that complexity is usualy hidden in an m4 macro package, a libfoo-config script or a pkgconfig/libfoo.pc file. I guess I should

Re: how to link with installed libltdl?

2005-09-01 Thread Howard Chu
Andreas Jellinghaus wrote: Howard Chu wrote: In OpenLDAP's configure.in we use ... so does libltdl never need any libraries linked to it? like -ldl on some systems or something else? all that complexity is usualy hidden in an m4 macro package, a libfoo-config script or a

Re: how to link with installed libltdl?

2005-09-01 Thread Bob Friesenhahn
On Thu, 1 Sep 2005, Howard Chu wrote: I guess I should better probe for libdl and link with it, too? anthing else? If you use libtool for linking, and the libltdl.la file is installed, then dependencies are taken care of automatically. If you're not using libtool for linking, then you're

Re: how to link with installed libltdl?

2005-09-01 Thread Andreas Jellinghaus
On Thursday 01 September 2005 12:30, Howard Chu wrote: If you use libtool for linking, and the libltdl.la file is installed, what about configure code? which configure macro will look for libltdl.la? can I use dnl use ltdl AC_CHECK_LIB(ltdl, lt_dlopen,, [AC_MSG_ERROR([libltdl not found])]) ?

Re: how to link with installed libltdl?

2005-09-01 Thread Andreas Jellinghaus
On Thursday 01 September 2005 16:52, Bob Friesenhahn wrote: So it seems that a libtool-provided macro should be used in configure.ac to test for an installed libltdl. Testing for it in a simple way could well indeed result in false negatives due to libltdl depending on some other library

Re: how to link with installed libltdl?

2005-09-01 Thread Ralf Wildenhues
Hi Andreas, * Andreas Jellinghaus wrote on Thu, Sep 01, 2005 at 08:28:24PM CEST: On Thursday 01 September 2005 16:52, Bob Friesenhahn wrote: I may be missing something, but all the libltdl-related macros I see are for the case of when libltdl is bundled with the package. I don't see

Re: how to link with installed libltdl?

2005-09-01 Thread Bob Friesenhahn
On Thu, 1 Sep 2005, Andreas Jellinghaus wrote: now I wonder: if the libtool *.la files contain all information about the dependencies etc, then shouldn't there be some macro that searches for that *.la files, gets the dependencies from it, does the compile and link test and sets up CFLAGS and

Re: how to link with installed libltdl?

2005-09-01 Thread Andreas Jellinghaus
On Thursday 01 September 2005 20:41, Ralf Wildenhues wrote: Dependent libraries it has, CFLAGS should not be necessary. Everything else would be a bug in ltdl. is there something that works like AC_CHECK_LIB, except that AC_CHECK_LIB seems to have no clue about *.la files, so is there