-
The GLIBC version on the compiling machine is too high, which causes the compiled file to be unable to run on the AWS machine |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 3 replies
-
same problem. |
Beta Was this translation helpful? Give feedback.
-
I wanna kown which version is no need GLIBC_2.34, because my centOS tried to make and failed twice. |
Beta Was this translation helpful? Give feedback.
-
same problem |
Beta Was this translation helpful? Give feedback.
-
same issue |
Beta Was this translation helpful? Give feedback.
-
If you are using Ubuntu do:
This solved the problem. It installs the gcc/g++ compilers and libraries. |
Beta Was this translation helpful? Give feedback.
-
It doesn't work |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, naabu is tied to the $ go install -v github.com/projectdiscovery/naabu/v2/cmd/naabu@latest This requires go + libpcap on the machine. |
Beta Was this translation helpful? Give feedback.
-
Ubuntu 20.04 can solve it |
Beta Was this translation helpful? Give feedback.
-
+1 Hmm... As default naabu is configured with a assumption that you are running it from VPS. |
Beta Was this translation helpful? Give feedback.
Unfortunately, naabu is tied to the
GLIBC_2.34
version installed on the GitHub worker box used to build the release binary. Generally, go is quite tolerant regarding the installed GLIBC version, but with naabu, it's tied to a specific version because of dynamic linking withlibpcap.
The best option would be to install naabu on the box via go install:
$ go install -v github.com/projectdiscovery/naabu/v2/cmd/naabu@latest
This requires go + libpcap on the machine.