"Please update your system curl." but I have super-latest curl

[TonalidadeHidrica]

I'm trying to install linuxbrew to a Devuan machine which I don't have sudo permission. Since the machine does not have curl installed, I manually compiled it from source and now placed at ~/.local/bin/curl. Then I tried to run the following script to install linuxbrew:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

only to obtain the following error message.

Error: Please update your system curl.
Minimum required version: 7.41.0
Your curl version:
Your curl executable: /home/username/.local/bin/curl
Failed during: /home/username/.linuxbrew/bin/brew update --force --quiet

I definitely have the latest version of curl, as you can see below. And actually linuxbrew does detect that curl is there, as shown in "Your curl executable".

$ which curl
/home/username/.local/bin/curl
$ curl --version
curl 7.78.0 (x86_64-pc-linux-gnu) libcurl/7.78.0 OpenSSL/3.0.0
Release-Date: 2021-07-21
Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTPS-proxy IPv6 Largefile NTLM NTLM_WB SSL TLS-SRP UnixSockets

But "Your curl version" is empty. So I guess the only issue is that homebrew cannot somehow parse the --version output to obtain the correct version information. How can I workaround?

[carlocab]

Try setting

export HOMEBREW_CURL=/path/to/curl
export HOMEBREW_DEVELOPER=1

Homebrew by default only looks for system-installed packages to use. There is experimental support for using a non-system curl, but it's gated by the HOMEBREW_DEVELOPER flag.

[Bo98]

If LD_LIBRARY_PATH is necessary, the linkage of your curl installation seems a bit broken, which ldd will likely indicate.

[TonalidadeHidrica]

@carlocab Thanks a lot. I'm currently trying to install curl and eventually force brew to use it.

@Bo98 Thanks for your advice. Without LD_LIBRARY_PATH, ldd ~/.local/bin/curl shows this:

ldd ~/.local/bin/curl
        linux-vdso.so.1 (0x00007fff2c32b000)
        libcurl.so.4 => /home/username/.local/lib/libcurl.so.4 (0x00007f55e6fca000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f55e6fa2000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f55e6de1000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f55e70b6000)
        libssl.so.3 => not found
        libcrypto.so.3 => not found

while when LD_LIBRARY_PATH is present, all library is located properly:

        linux-vdso.so.1 (0x00007ffcd29d9000)
        libcurl.so.4 => /home/username/.local/lib/libcurl.so.4 (0x00007fc30f392000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc30f36a000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc30f1a9000)
        libssl.so.3 => /home/username/.local/lib64/libssl.so.3 (0x00007fc30f101000)
        libcrypto.so.3 => /home/username/.local/lib64/libcrypto.so.3 (0x00007fc30eca1000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fc30f47e000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc30ec9a000)

I guess this means that curl is dynamically linked to libssl and libcrypto. Should I somehow link them statically?

[Bo98]

Curl was probably expecting them in /home/username/.local/lib but you have them installed in /home/username/.local/lib64 - just a mismatch in install directories between how OpenSSL was installed and how Curl was installed.

[TonalidadeHidrica]

Ah, I see. I installed both of them from source with the same --prefix= option, but it is now different. I don't know why. But maybe I should double-check the process. Thanks a lot!

[carlocab]

Usually the --libdir= flag helps. You'll probably want to keep a working non-Homebrew curl around. I've on occasion broken my Homebrew curl installation (always my fault), but fixing it often requires a working curl.

[TonalidadeHidrica]

It worked! So the solution is as follows.

• First, try installing curl with homebrew. If you have LD_LIBRARY_PATH issue, you may temporarily set export HOMEBREW_NO_ENV_FILTERING=1 variable.
• Once you succeeded in installing, set export HOMEBREW_FORCE_BREWED_CURL=1. Then there will be no warning, no errors. Maybe we may write it in .profile.