Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Feb 2021 20:03:56 -0800
From:      Pete Wright <pete@nomadlogic.org>
To:        freebsd@dreamchaser.org, FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: which linux libfuse.so.2?
Message-ID:  <51a444f0-c920-1764-0480-ca99e2ac8186@nomadlogic.org>
In-Reply-To: <c55fa527-c0fe-97f2-d9d9-bc01aa092e23@dreamchaser.org>
References:  <79254130-e926-fab3-9d5b-b6862c6b747b@dreamchaser.org> <8e50ba4b-a419-0d60-c2b5-1c379e2dc604@nomadlogic.org> <c55fa527-c0fe-97f2-d9d9-bc01aa092e23@dreamchaser.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help


On 2/9/21 7:23 PM, Gary Aitken wrote:
>
> Is there a way to run /compat/linux/usr/bin/ldd to figure out what it is
> really looking for?  I get the same error whether the symlink for 
> libfuse.so.2
> is present or not.  If I try to run the linux ldd I get:
>
> $ /compat/linux/usr/bin/ldd 
> PrusaSlicer-2.3.0+linux-x64-202101111322.AppImage
> bash: /compat/linux/usr/bin/ldd: /usr/bin/bash: bad interpreter: No 
> such file or directory
>
> There is no /usr/bin/bash (it's in /usr/local/bin/bash), but there is a
> /compat/linux/usr/bin/bash.
>

you might want to chroot into the /compat/linux environment like this 
for example:
$ sudo chroot /compat/linux /usr/bin/bash

that should make tools like ldd friendlier while you debug.

you also might want to give setting your LD_LIBRARY_PATH when executing 
the command from freebsd to include the linux locations and see how far 
you get:
$ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/compat/linux/lib:/compat/linux/lib64 
PrusaSlicer...

-p

-- 
Pete Wright
pete@nomadlogic.org
@nomadlogicLA




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?51a444f0-c920-1764-0480-ca99e2ac8186>