On 2021-07-17, Kent Watsen wrote:
> Thanks Theo!
>
>
>> It seems you copied libjq and libonig into usr/local/lib in the chroot.
>> By default, ld.so only looks for shared objects in /usr/lib, so it can't
>> find them.
>>
>> # env LD_LIBRARY_PATH=/usr/lib:/usr/local/lib chroot /var/www
>>
Thanks Theo!
> It seems you copied libjq and libonig into usr/local/lib in the chroot.
> By default, ld.so only looks for shared objects in /usr/lib, so it can't
> find them.
>
> # env LD_LIBRARY_PATH=/usr/lib:/usr/local/lib chroot /var/www
> /usr/local/bin/jq --version
>
> should work.
On Fri, Jul 16, 2021 at 10:24:10PM +, Kent Watsen wrote:
> I’ve spent a few hours on this and am lost. I have plenty experience moving
> executables into a chroot environments, but `jq` is proving to be
> exceptionally difficult.
>
> The executable is found when chrooted to ‘/‘ but not '
Easy button for putting all the dependency files into the chroot:
# for f in `ldd /usr/local/bin/jq | grep '0' | awk '{print $7}'`; do
d=`dirname $f | sed 's#^/##’`
mkdir -p /var/www/$d
I’ve spent a few hours on this and am lost. I have plenty experience moving
executables into a chroot environments, but `jq` is proving to be exceptionally
difficult.
The executable is found when chrooted to ‘/‘ but not ' /var/www’. Yes, of
course I copied all the files referenced from `ldd`
5 matches
Mail list logo