libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

libtool related build questions


From: Bob Rossi
Subject: libtool related build questions
Date: Thu, 14 Dec 2006 13:35:35 -0500
User-agent: Mutt/1.5.12-2006-07-14

On Thu, Dec 14, 2006 at 07:11:08PM +0100, Ralf Wildenhues wrote:
> > What exactly can I do about the libtool warning messages?
> 
> These?

Yup,

> >   *** Warning: This system can not link to static lib archive 
> > /home/bobbybrasko/log4cxx/apr-util/src/prefixdir/lib/libaprutil.la.
> >   *** I have the capability to make that library automatically link in when
> >   *** you link to this library.  But I can only do this if you have a
> >   *** shared version of the library, which you do not appear to have.
> 
> They are sometimes bogus.  Nobody has gotten around to fixing that yet.

OK, That's interesting. I wonder if this is OK then. Is there a way to
tell if it's bogus or not?

> > is the -enable-experimental-libtool something this list endorses? 
> 
> FWIW, I have no idea what it does.  Is there documentation for it, or
> source to read?  Where does it come from?

I learned about this swich from the apr folks. http://apr.apache.org/
This is a quote from someone,
  It uses jlibtool, Justin's replacement for libtool.                           
                          
                                                                                
                          
  The source code for it is here:                                               
                          
  http://svn.apache.org/repos/asf/apr/apr/trunk/build/jlibtool.c                
                          

I thought maybe there was some connection between libtool and this
option/project. If not, sorry.

> > BTW, OUCH, I just realized I configured with the wrong parameter, 
> > -enable-experimental-libtool should have been --enable-experimental-libtool.
> 
> All I know is -enable-foo and --enable-foo are equivalent.

OK, that's why re running configure with --enable-experimental-libtool
didn't change a thing :). Thanks for the insight.

> Where are the XML_ParserFree and other functions located at?
> Do you have a URL for the tarball you're building?

I'm building apr, and apr-util from here,
  http://apr.apache.org/anonsvn.html
and I'm building log4cxx from here,
  http://logging.apache.org/site/cvs-repositories.html

I've built them all with mingw, and all of these packages, from what I
can tell, use libtool. 

XML_ParserFree comes from here,
 apr-util/src/apr-util/xml/expat/lib/expat.h:XML_ParserFree(XML_Parser parser);
which in turn, when I configured it, gave this message:

  *** Warning: This system can not link to static lib archive 
/home/bobbybrasko/log4cxx/apr-util/src/apr-u
  *** I have the capability to make that library automatically link in when
  *** you link to this library.  But I can only do this if you have a
  *** shared version of the library, which you do not appear to have.

  *** Warning: This system can not link to static lib archive 
/home/bobbybrasko/vigilant/apr/apr-1.3.0-cvs
  *** I have the capability to make that library automatically link in when
  *** you link to this library.  But I can only do this if you have a
  *** shared version of the library, which you do not appear to have.
  libtool: link: warning: undefined symbols not allowed in i686-pc-mingw32 
shared libraries
  gawk -f /home/bobbybrasko/vigilant/apr/apr-1.3.0-cvs/build-1/make_exports.awk 
/home/bobbybrasko/log4cxx/
  gawk -f 
/home/bobbybrasko/vigilant/apr/apr-1.3.0-cvs/build-1/make_var_export.awk 
/home/bobbybrasko/log4c
  gcc -E -DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE   
-I/home/bobbybrasko/log4cxx/apr-util/src/apr-util/include
  gcc -E -DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE   
-I/home/bobbybrasko/log4cxx/apr-util/src/apr-util/include
  sed 's,^\(location=\).*$,\1installed,' < apu-1-config > apu-config.out
  make[1]: Leaving directory `/home/bobbybrasko/log4cxx/apr-util/src/apr-util'

Any ideas?

Thanks,
Bob Rossi




reply via email to

[Prev in Thread] Current Thread [Next in Thread]