On Thu, 25 Jun 2009 10:36:22 -0500, Karl Lehenbauer wrote
> Yeah I was getting all those warnings too.  With the updated files  
> from libtool and TEA, it did silence the complaining on my machines.
> 

good. 

I wonder if the AC_CONFIG_MACRO_DIR is enough for enabling
the autotools to find all they need. Using the macro should be a more
stable solution....

by the way, I keep getting messages like

svn: OPTIONS of 'https://svn.apache.org/repos/asf/tcl/rivet/trunk': could not
connect to server (https://svn.apache.org)

when i try to update my working copy,
anyone else is experiencing the same problem?

 -- Massimo


> On Jun 24, 2009, at 8:21 PM, Massimo Manghi wrote:
> 
> > I can't remember what exactly I did introducing this macro
> > and svn.apache.org seems to be down at the moment to read
> > the logs. I'm quite certain I added ACLOCAL_AMFLAGS = -I m4
> > to Makefile.am
> >
> > I tried to rebuild the configure script in the way
> > you did and my libtool installation (2.2.6) suggested to put
> >
> > AC_CONFIG_MACRO_DIR([m4])
> >
> > in configure.ac. It seems that a working 'configure' comes out of it.
> >
> > more recent libtool versions complain a lot with warnings like this
> >
> > configure.ac:93: warning:  
> > AC_CACHE_VAL(lt_prog_compiler_pic_works, ...):
> > suspicious cache-id, must contain _cv_ to be cached
> > tclconfig/libtool.m4:568: AC_LIBTOOL_COMPILER_OPTION is expanded
> > from...
> > tclconfig/libtool.m4:4559: AC_LIBTOOL_PROG_COMPILER_PIC is expanded
> > from...
> >
> > I hope the new libtool.m4 will silence these messages, but I still  
> > can't get
> > to svn.apache.org to find out
> >
> > -- Massimo
> >
> > On Wed, 24 Jun 2009 14:34:24 -0500, Karl Lehenbauer wrote
> >> I added
> >>
> >> m4_include([m4/ax_prefix_config_h.m4])
> >>
> >> to acinclude.m4, and the configure script works now.
> >>
> >> -karl
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >
> >
> > --
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


--


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to