[Top][All Lists]

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

Re: configuring libtool on 10.3.3 and/or multiple symbol definitions

From: Randall Skelton
Subject: Re: configuring libtool on 10.3.3 and/or multiple symbol definitions
Date: Thu, 25 Mar 2004 20:51:10 -0500 (EST)

Thanks for your reply Peter.

While I am using libtool for a couple of projects now, it is still rather
new to me.  

./libtool --version (GNU libtool) 1.5 (1.1220 2003/04/05 19:32:58)

By 'libtoolize' I suppose you mean:

  cp /usr/share/aclocal/libtool.m4 ./acinclude.m4
  glibtoolize --force
  automake --add-missing

Sure enough, it builds now!  Many, thanks!  My main reason for using
libtool is to make it easier for others to build the code...
Does everyone need to 'libtoolize' prior to building?  If not, under what
circumstances should they?

With regards to bootstrapping HEAD or branch-1-5, I am using the latest
releases (not CVS) for both autoconf and automake.  


On Fri, 26 Mar 2004, Peter O'Gorman wrote:

> Randall Skelton wrote:
> > I seem to be having troubles getting the cvs code to configure on OS X 
> > 10.3.
> You'd need to install the latest release autoconf and automake etc. first to 
> get HEAD bootstrapped.
> > Alternatively, perhaps someone can explain how to avoid multiple 
> > definitions of symbols using the stock developer tools version of libtool:
> I think you may be barking up the wrong tree here. Did you rerun libtoolize 
> --force for this project? This looks like the "convenience library bug" 
> which implies a libtool < 1.4.3. Please note that the libtool used to build 
> a package is not the glibtool sitting in /usr/bin, it is the libtool sitting 
> in the build directory. If you type './libtool --version' in the build 
> directory, what does it say?
> Peter
> -- 
> Peter O'Gorman -

reply via email to

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