Date: Thu, 1 Apr 2004 09:38:38 -0800 From: paul beard <paulbeard@mac.com> To: FreeBSD-questions <questions@Freebsd.org> Subject: Re: some anomalies in my system? Message-ID: <693D7BE5-8403-11D8-B5EE-000A95BBCCF8@mac.com> In-Reply-To: <20040401052144.GB62275@xor.obsecurity.org> References: <4A8DE066-838D-11D8-B5EE-000A95BBCCF8@mac.com> <20040401035806.GA60999@xor.obsecurity.org> <294497F9-8395-11D8-B5EE-000A95BBCCF8@mac.com> <20040401044859.GA61997@xor.obsecurity.org> <9D2F6AF8-8399-11D8-B5EE-000A95BBCCF8@mac.com> <20040401052144.GB62275@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail-24--545295771
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
On Mar 31, 2004, at 9:21 PM, Kris Kennaway wrote:
> OK, feel free to ignore my advice as you see fit.
>
Looking back through the thread, you asked if I had installed any
non-ports software or some other variant of libtool: the answer was no.
I didn't see any advice, so I took the initiative to find out what
libtool might be doing. I did discover that there was a dependency on a
deprecated version of libtool (1.3 where 1.5 seems to be the
current/preferred version). And I was able to get around my problem by
working from the distfiles and leaving out whatever the ports system
was doing (that was where the inability to build shlibs was getting in
the mix). As noted in my followup post to the list, once I installed
from the {$PORTDIR}/work/<portname> directory, all went well and I have
now resolved my problem.
Apologies if I offended. The insight on libtool is appreciated.
--
Paul Beard
<www.paulbeard.org/>
paulbeard [at] mac.com
--Apple-Mail-24--545295771--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?693D7BE5-8403-11D8-B5EE-000A95BBCCF8>