Re: Compiling https://gnuwget.gitlab.io/wget2/wget2-latest.tar.gz into a local path/dir to run?

[Tim Rühsen]

Hi,

On 11.03.23 07:54, Ant wrote:
> Hello,
>
> In my updated 64-bit Debian bullseye OS, I followed
> https://gitlab.com/gnuwget/wget2's instructions on downloading and
> building from https://gnuwget.gitlab.io/wget2/wget2-latest.tar.gz.
> However, I didn't want to use its "sudo make install" since I didn't
> want to install to clean Debian globally. I just wanted to keep it local
> in my account. I moved my ~/Downloads/wget2-2.0.1/src/wget2 into ~/bin/,
> and tried to run wget2 but it gave me this error:
>
> ./wget2: error: '/home/ant/bin/.libs/wget2' does not exist
>
> It seems to depend on other files. How can I compile and run for my local
> account only?
>
> Thank you for reading and hopefully answering soon. :)

The `sudo` only needs to be done because the default install directory 
belongs to root.

You can set the default install directory with the --prefix=<directory> 
./configure option. If you have write permissions to that directory, you 
don't need sudo.

If you build a dynamic executable, you need to tell your system/loader 
where to find those libraries. On linux you normally can add the library 
directory to a file in `/etc/ld.so.conf.d/`. Use `sudo ldconfig` to 
update caches.

But maybe your library path is already known, then you just have to 
`sudo ldconfig` to update the loader cache.

The details may differ on your system, but this should point you into 
the right direction :)

Regards, Tim

OpenPGP_signature
Description: OpenPGP digital signature