[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-ports
Subject:    Re: libtool warning
From:       Gerardo Santana Gomez Garrido <santana () openbsd ! org ! mx>
Date:       2002-06-20 1:58:16
[Download RAW message or body]

Would you mind pointing me out where are the resources you are talking \
about? Because I have searched in the patches in the ports tree and didn't \
find a reference to libtool 1.4.x

On Mon, Jun 10, 2002 at 08:47:25PM -0600, Brad wrote:
> Please actually look at the resources in the ports tree, you're wasting
> your time e-mailing the list when this stuff has already been taken care
> of many times in the ports tree with pretty much all the permutations of
> libtool.
> 
> > Date: Mon, 10 Jun 2002 20:48:18 -0500
> > From: Gerardo Santana Gomez Garrido <santana@openbsd.org.mx>
> > To: jolan <jolan@enteract.com>
> > Cc: "Benninghoff, John" <John.Benninghoff@rbcdain.com>, \
> >                 ports@openbsd.org
> > Subject: Re: libtool warning
> > 
> > I found a patch from beck@openbsd.org in libtool mailing list, but it \
> > was for libtool-current I remember.
> > 
> > Maybe Beck could patch 1.4e...
> > 
> > 
> > On Mon, Jun 10, 2002 at 05:51:54PM -0500, jolan wrote:
> > > re-read what marc wrote. the libtool in ports is 1.3.5. a lot of \
> > > newer programs happen to use 1.4.x. it may seem to work or work fine, \
> > > but it may become an issue later on down the road. best to stay safe \
> > > for everybody's sake and patch the program's 1.4.x libtool rather \
> > > than use 1.3.5 and pray for compatability.
> > > 
> > > -jolan
> > > 
> > > > Right off the bat I'd say, check the version of libtool you're \
> > > > dealing with (my bet is 1.4.x).  If it's 1.3.x then there are \
> > > > in-tree patches.  If it's 1.4.x then check out what some of the \
> > > > other ports have done.  The situation is a bit of a mess as libtool \
> > > > is a moving target. 
> > > > Marc
> > > 
> > > 
> > > 
> > > On Mon, 10 Jun 2002, Benninghoff, John wrote:
> > > 
> > > > Correct me if I'm wrong, but isn't that what USE_LIBTOOL is for ? \
> > > > (use the fixed libtool from the ports tree instead of the provided \
> > > > libtool) 
> > > > I have used this sucessfully to work around a broken libtool, but \
> > > > there doesn't seem to be much documentation/discussion (or even \
> > > > use) of the setting. 
> > > > -----Original Message-----
> > > > From: Marc Matteo [mailto:marcm@lectroid.net]
> > > > Sent: Friday, May 31, 2002 8:27 PM
> > > > To: Gerardo Santana Gomez Garrido
> > > > Cc: ports@openbsd.org
> > > > Subject: Re: libtool warning
> > > > 
> > > > 
> > > > On Fri, 31 May 2002, Gerardo Santana Gomez Garrido wrote:
> > > > 
> > > > > kdevelop has its own libtool and I get the following warning when \
> > > > > faking. I guess that's the problem:
> > > > 
> > > > Welcome to libtool hell.
> > > > 
> > > > > libtool: install: warning: `./dbg/libkdevelopdbg.la' has not been
> > > > > installed in ` /usr/local/lib'
> > > > > 
> > > > > any ideas?
> > > > 
> > > > These shouldn't be a problem (someone correct me if it is) it's \
> > > > just libtool whining, confused by our fake setup.  What WILL be a \
> > > > problem if you havn't addressed some of libtool's other quirks \
> > > > (like how it thinks OpenBSD links libs).
> > > > 
> > > > Marc
> > > > 
> > > > 
> > > > 
> > 
> > --
> > Gerardo Santana Gómez Garrido
> > http://www.openbsd.org.mx/~santana/
> > OpenBSD México

-- 
Gerardo Santana Gómez Garrido
http://www.openbsd.org.mx/~santana/
OpenBSD México


[prev in list] [next in list] [prev in thread] [next in thread]