On Fri, 18 Jan 2002, Ulric Eriksson wrote:
> If this were on Linux, I would tell you to run /sbin/ldconfig -v, but I
> don't know if that's necessary with OpenBSD.
ldconfig runs on boot, but generally it's not required for OpenBSD. I've
tried both rebooting and manually running it, but no luck.
> Check config.log. It reports what the configure script did and what went
> wrong. In this case, why it couldn't find the library.
config.log doesn't seem to be too helpful:
configure:7754: checking for main in -lMowitz
configure:7774: gcc -o conftest -g -O2 -L/usr/X11R6/lib conftest.c
-lMowitz -lXaw -lXpm -lXmu -lXext -lSM -lICE -lXt -lX11 -lm >&5
ld: -lMowitz: no match
collect2: ld returned 1 exit status
configure:7777: $? = 1
configure: failed program was:
#line 7762 "configure"
ldconfig -r lists the libraries ld knows about:
84:-lXm.2.1 => /usr/local/lib/libXm.so.2.1
85:-lbz2.10.1 => /usr/local/lib/libbz2.so.10.1
86:-lXawM.1.0 => /usr/local/lib/libXawM.so.1.0
87:-lMowitz.1.1 => /usr/local/lib/libMowitz.so.1.1
I'm not too knowledgable about the way libraries are referenced, but
perhaps the configure script doesn't realize "lMowitz.1.1" is "lMowitz"
itself. I believe a similiar bug popped up when I was trying to
configure Mowitz to use Xaw3D instead of XawM (I ended up installing
XawM in the end). Apart from Mowitz and Siag, I haven't had this
problem with any other software I've compiled. Then again, I tend not to
compile large programs on my puny Sparc 5/85. ;)
Any help, as always, would be most appreciated!
--Imad "(e)magius" Hussain
"Many that live deserve death. And some that die deserve life. Can you
give it to them? Then do not be too eager to deeal out death in
judgement. For even the very wise cannot see all ends."
--J.R.R. Tolkien via Gandalf, Book One of _Lord of the Rings_
This archive was generated by hypermail 2.1.2 : Fri Jan 18 2002 - 22:34:31 CET