You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered a problem after compiling proxychains4 on my Debian 11 VM.
I compiled the newest source with "./configure && make && make install" and tested with
"proxychains4 ping" and got the result: [proxychains] config file found: /etc/proxychains.conf [proxychains] preloading /usr/local/lib/libproxychains4.so [proxychains] DLL init ping: symbol lookup error: /usr/local/lib/libproxychains4.so: undefined symbol: dlsym
I fixed the problem and got a working libproxychains4.so by changing "./configure" script line 108 from echo OS_LDFLAGS=-pthread -ldl -Wl,--no-as-needed>>config.mak
to echo OS_LDFLAGS=-pthread -Wl,--no-as-needed -ldl>>config.mak
as suggested in the thread. (And "make clean&&configure&&make&&make install")
Is there a reason the configure-script contains the arguments in this order and not the (for me) working one or can this be changed?
Julian
The text was updated successfully, but these errors were encountered:
Hi!
I encountered a problem after compiling proxychains4 on my Debian 11 VM.
I compiled the newest source with "./configure && make && make install" and tested with
"proxychains4 ping" and got the result:
[proxychains] config file found: /etc/proxychains.conf [proxychains] preloading /usr/local/lib/libproxychains4.so [proxychains] DLL init ping: symbol lookup error: /usr/local/lib/libproxychains4.so: undefined symbol: dlsym
After googling for a bit I found this thread:
https://stackoverflow.com/questions/27607130/undefined-reference-to-dlsym-and-dlopen?rq=1
I fixed the problem and got a working libproxychains4.so by changing "./configure" script line 108 from
echo OS_LDFLAGS=-pthread -ldl -Wl,--no-as-needed>>config.mak
to
echo OS_LDFLAGS=-pthread -Wl,--no-as-needed -ldl>>config.mak
as suggested in the thread. (And "make clean&&configure&&make&&make install")
Is there a reason the configure-script contains the arguments in this order and not the (for me) working one or can this be changed?
Julian
The text was updated successfully, but these errors were encountered: