Re: AC_LIBTOOL_WIN32_DLL for libgfortran [also Re: Updating libtool in GCC and srctree]

For example, this AC_LIBTOOL_WIN32_DLL macro was removed/deprecated from libtool three years ago. What should be used with a recent libtool? And where is it documented? There is no need for any special consideration to create a DLL with modern libtool. One just needs --enable-shared at

Re: Updating libtool in GCC and srctree

On Mon, Mar 12, 2007 at 04:03:52PM -0700, Steve Ellcey wrote: configure:15448: error: possibly undefined macro: AM_PROG_GCJdnl Where'd that come from? Wherever it is, it's a bug. Maybe someone checked in a typo to the configure file. dnl is a comment start token in autoconf (that's a very

Re: Updating libtool in GCC and srctree

On Mon, Mar 12, 2007 at 04:03:52PM -0700, Steve Ellcey wrote: configure:15448: error: possibly undefined macro: AM_PROG_GCJdnl Where'd that come from? Wherever it is, it's a bug. Maybe someone checked in a typo to the configure file. dnl is a comment start token in autoconf (that's a

Re: Updating libtool in GCC and srctree

On Mar 9, 2007, Steve Ellcey [EMAIL PROTECTED] wrote: If I just run autoconf I get errors because I am not including the new ltoptions.m4, ltsugar.m4, and ltversion.m4 files. I'd just prepend them to our local copy of libtool.m4, pretty much like aclocal would have done into aclocal.m4. But

Re: Updating libtool in GCC and srctree

So, you need to run aclocal with: $ aclocal -I ../config -I .. -- albert chin ([EMAIL PROTECTED]) Thanks, that helps a lot. For libstdc++-v3 I actually needed -I . as well in order to find linkage.m4 so maybe -I . -I .. -I ../config is the best option list to use on aclocal calls in the

Re: Updating libtool in GCC and srctree

Joseph S. Myers [EMAIL PROTECTED] writes: We should use current CVS HEAD libtool. We definitely can't use 1.5 releases without *a lot* of auditing of local changes: we've allowed local changes into GCC's libtool on the basis that there are equivalents in CVS HEAD (this is the policy in

Re: Updating libtool in GCC and srctree

I have made some progress in updating libtool in the src (binutils) tree and I have attached the various changes (but not the actual new libtool files) to this email in case anyone wants to see what I am doing. I am having more trouble with the GCC tree. I put the new libtool in the toplevel

Re: Updating libtool in GCC and srctree

Steve Ellcey [EMAIL PROTECTED] writes: $ aclocal autom4te: unknown language: Autoconf-without-aclocal-m4 aclocal: autom4te failed with exit status: 1 Looks like you have an out-of-date autom4te.cache. Andreas. I removed autom4te.cache and reran aclocal. Same results. Steve Ellcey

Re: Updating libtool in GCC and srctree

On Fri, Mar 09, 2007 at 03:58:40PM -0800, Steve Ellcey wrote: I am having more trouble with the GCC tree. I put the new libtool in the toplevel directory, just like I did in the binutils src tree and then I went to the boehm-gc (and libffi) directories to try and rerun autoconf. If I just

Updating libtool in GCC and srctree

Now that autoconf has been updated to 2.59, I would like to update the libtool that GCC and the binutils/gdb/etc use. Unfortunately, I am not having much luck coming up with a patch and figuring out what all needs to be reconfigured. Here is what I have tried so far. In the libtool

Re: Updating libtool in GCC and srctree

Steve Ellcey [EMAIL PROTECTED] writes: I downloaded the 2.1a snapshot of libtool and found Are you sure you want to use the (rather oldish) 2.1a snapshot? I think you'll better off using the latest stable release which is 1.5.22. ltmain.sh in libltdl/config/ltmain.sh, I copied that to the

Re: Updating libtool in GCC and srctree

I downloaded the 2.1a snapshot of libtool and found Are you sure you want to use the (rather oldish) 2.1a snapshot? I think you'll better off using the latest stable release which is 1.5.22. I thought that 2.1a was a snapshot of ToT. I have some recollection of someone saying we would

Re: Updating libtool in GCC and srctree

On Fri, 9 Mar 2007, Andreas Schwab wrote: Steve Ellcey [EMAIL PROTECTED] writes: I downloaded the 2.1a snapshot of libtool and found Are you sure you want to use the (rather oldish) 2.1a snapshot? I think you'll better off using the latest stable release which is 1.5.22. We should use

Re: Updating libtool in GCC and srctree

Steve Ellcey [EMAIL PROTECTED] writes: I downloaded the 2.1a snapshot of libtool and found Are you sure you want to use the (rather oldish) 2.1a snapshot? I think you'll better off using the latest stable release which is 1.5.22. I thought that 2.1a was a snapshot of ToT. Sorry, I was

Re: Updating libtool in GCC and srctree

On Mar 8, 2007, Steve Ellcey [EMAIL PROTECTED] wrote: You'll still need libtool.m4. Are you sure? Yep. You can do away without a manually-managed libtool.m4 if you use aclocal and you trust it will always bring in the right version of libtool.m4 (i.e., in the one that is compatible with the

Re: Updating libtool in GCC and srctree

On Thursday 08 March 2007, Steve Ellcey wrote: You'll still need libtool.m4. Are you sure? According to http://www.gnu.org/software/libtool/manual.html#Distributing we shouldn't need libtool.m4 in our package. i'm pretty sure those guidelines are for people making their final