Error: Can't find libjava.so
Marcel Grandemange
thavinci at thavinci.za.net
Mon Sep 15 19:35:26 UTC 2008
> > I do realize this is probably better suited for freebsd-questions ,
> however
> > haven't received any response and was simply hoping someone would be
kind
> > enough.
> >
> > I recently obtained a very decent ups, however it is not supported by
NUT.
> >
> > It does however come with winpower software that does run on FreeBSD.
> >
> > However it rewuired java.
> >
> > So installed from ports
> >
> > And was presented with following error:
> >
> > Error: can't find libjava.so
> >
> > This is on system in folder
> "/usr/local/Diablo-jre1.6.0/lib/amd64/libjava.so
>
> >Can you provide the output of "ldconfig -r" from that box? I have
> >a feeling the ld.so pathing hints might lack a directory or two.
>
>
> /var/run/ld-elf.so.hints:
> search directories: /lib:/usr/lib:/usr/lib/compat:/usr/local/lib
>This is the problem as I see it. ld.so, which is used for finding and
>loading shared libraries, is not configured to look in
>/usr/local/Diablo-jre1.6.0/lib/amd64 for libraries.
>I'd like to know which port you installed, and how you installed it.
I did a cvsup on ports to update to latest on FreeBSD7.0 release amd64
Used port /usr/ports/java/Diablo-jre16
Simply did
Make
Make install
Make clean
Nothing Fancy...
>Based on the above, it appears to me the port itself may/does have a bug
>-- it should be updating the hints path to include that directory, but
>does/is not. Please note I am in no way shape or form familiar with
>Java or this port.
Would make sense!
>I do not know if this is specific to your machine or not -- however,
>this is the first time I've seen it mentioned, and I quite active with
>freebsd-ports. (I'm subscribed to 15 separate FreeBSD mailing lists,
>and I read/follow them all)
I have not tested this on any other machine, was doing this in a virtual
machine to test ups software before deploying...
>Regarding the problem itself: there are ways to work around this by
>using the environment variable LD_LIBRARY_PATH. I do not recommend
>this, though -- properly configuring the ld.so search path when a
>program (or port) is installed is the proper method.
Could you advise me how to do this? Hope you don't mind!
>Cross-posting to multiple lists is generally shunned upon, so answers to
>the above questions will help determine if the discussion should be
>moved to freebsd-ports@ or not. I've a feeling it should be.
>Thanks!
Fare Enough!
Thank You!
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
__________ NOD32 3443 (20080915) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
More information about the freebsd-hackers
mailing list