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
Working through this issue with expat not building shared libs, the
maintainer noticed this:
creating libtool
checking host system type... i386-unknown-kfreebsd4.9-gnu
checking whether to build shared libraries... no
checking whether to build static libraries... yes
what isn't letting us build
On Wed, Mar 31, 2004 at 07:33:06PM -0800, paul beard wrote:
Working through this issue with expat not building shared libs, the
maintainer noticed this:
creating libtool
checking host system type... i386-unknown-kfreebsd4.9-gnu
checking whether to build shared libraries... no
checking
On Mar 31, 2004, at 7:58 PM, Kris Kennaway wrote:
It still looks like you have a bogus
non-ports version of libtool installed that is providing the wrong
information to the configure script.
I took that as a hint to look at the versions of libtool: there wasn't
a version I didn't have
On Wed, Mar 31, 2004 at 08:29:26PM -0800, paul beard wrote:
On Mar 31, 2004, at 7:58 PM, Kris Kennaway wrote:
It still looks like you have a bogus
non-ports version of libtool installed that is providing the wrong
information to the configure script.
I took that as a hint to look at
On Mar 31, 2004, at 8:48 PM, Kris Kennaway wrote:
I took that as a hint to look at the versions of libtool: there wasn't
a version I didn't have installed, so I removed them all and decided
to
let them get handled as dependencies.
That's not what I asked.
I realize that, but that was the first
On Wed, Mar 31, 2004 at 09:01:19PM -0800, paul beard wrote:
On Mar 31, 2004, at 8:48 PM, Kris Kennaway wrote:
I took that as a hint to look at the versions of libtool: there wasn't
a version I didn't have installed, so I removed them all and decided
to
let them get handled as
