Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Could not find Xprint lib (libXp.so.6) in debian stretch

61 views
Skip to first unread message

Joao Roscoe

unread,
May 11, 2018, 10:20:04 AM5/11/18
to
In my environment, I run several applications from a remote NFS filesystem, mounted at /opt/tools. Those are 32bits binaries and I'm running stretch-amd64, but multiarch appears to be solving that, so far.

However, trying to run nedit (Nirvana Editor) from that mount resulted in the familiar missing library error:

> nedit: error while loading shared libraries: libXp.so.6: cannot open shared object file: No such file or directory

I took a look at debian packages search, and could not find that library (it was available in jessie).

Of course, nedit package *is* available, and works, but using that would break a standard: some development tools should be available in /opt/tools

How could I solve this? Would it be possible to get libXp6 in stretch?

Best regards,
Joao

Greg Wooledge

unread,
May 11, 2018, 10:30:04 AM5/11/18
to
On Fri, May 11, 2018 at 11:17:43AM -0300, Joao Roscoe wrote:
> > nedit: error while loading shared libraries: libXp.so.6: cannot open
> shared object file: No such file or directory
>
> I took a look at debian packages search, and could not find that library
> (it was available in jessie).
>
> Of course, nedit package *is* available, and works, but using that would
> break a standard: some development tools should be available in /opt/tools
>
> How could I solve this? Would it be possible to get libXp6 in stretch?

If the jessie package still works, just use that.

Joao Roscoe

unread,
May 11, 2018, 11:20:04 AM5/11/18
to
Thank you for your attention!

Wouldn't it be risky to the system installing another release's package?
How should I change sources.list to allow that?

Best regards,
João

Greg Wooledge

unread,
May 11, 2018, 11:30:05 AM5/11/18
to
On Fri, May 11, 2018 at 12:14:07PM -0300, Joao Roscoe wrote:
> Wouldn't it be risky to the system installing another release's package?
> How should I change sources.list to allow that?

Using a shared lib package from one release ago? No, people do that all
the time. Usually just as a result of upgrading from the old release
to the new one, and having the old shared libs stick around. But
sometimes, if you DIDN'T upgrade, you may actually need to hunt down the
older package and install it.

For example, I have a locally built xv pacakge that depends on libpng12-0.
But libpng12-0 is not available in stretch (it was replaced by a newer
libpng with a completely different API). On machines that I upgraded
from jessie, there's no problem -- I can install my xv package and use
jessie's libpng12-0 library. But on new stretch installs, libpng12-0
can't be installed automatically, because apt doesn't know about it.
So I either have to download it from packages.debian.org by hand, or
temporarily set up a jessie line in sources.list.

Joao Roscoe

unread,
May 11, 2018, 11:50:04 AM5/11/18
to
Understood.
In simple words, the easy way would be downloading the proper deb, and using "dpkg -i" on it, right?

João

Joao Roscoe

unread,
May 11, 2018, 2:50:04 PM5/11/18
to
It worked perfectly. Thank you for your time.

Best regards,
Joao
0 new messages