This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libgfortran Makefile question (using latest libtool)
- From: "Charles Wilson" <cygwin at cwilson dot fastmail dot fm>
- To: "Steve Ellcey" <sje at cup dot hp dot com>
- Cc: gcc at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Wed, 21 Mar 2007 20:22:01 -0400
- Subject: Re: libgfortran Makefile question (using latest libtool)
- References: <200703212149.OAA00770@hpsje.cup.hp.com>
On Wed, 21 Mar 2007 14:49:43 -0700 (PDT), "Steve Ellcey" said
> > From: Charles Wilson <xxxx@xxxxxxx>
^^^^^^^^^^^^^
fix your mailer
> > The --tag option is added by automake-1.9 or automake-1.10, but not 1.8:
>
> Interesting, the Makefile.in in libgfortran claims to be from automake
> 1.9.6. If I run this automake in a tree with the old (1.4 based
> libtool) I don't get any --tags options in Makefile.in, but if I run
> automake in the tree where I have the latest libtool then I see the
> --tag option used. So I guess just rerunning automake is sufficient to
> fix this problem.
Well, I should have been more specific. The --tag option is added by
am-1.10 or 1.9 IF automake detects that your current libtool supports
the --tag option, and that your current libtool supports that specific
language.
if ($lang->libtool_tag && exists $libtool_tags{$lang->libtool_tag})
So, it's not surprising that the "old" Makefile.in, generated with
am-1.9, did not contain the appropriate --tag option, because the
ancient libtool the existed in-tree and was used when that old
Makefile.in was generated did not support --tag.
BTW, did you see this message:
Re: AC_LIBTOOL_WIN32_DLL for libgfortran [also Re: Updating libtool in
GCC and srctree]
http://gcc.gnu.org/ml/gcc/2007-03/msg00658.html
It actually didn't get threaded in the archives under EITHER of the two
topics...
--
Chuck