rofl0r / rofl0r/proxychains-ng
How m2 chip should use proxychains4
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
I installed it directly using homebrew and compiled it myself, but the following error occurred.
[proxychains] preloading /usr/local/lib/libproxychains4.dylib
dyld[5482]: terminating because inserted dylib '/usr/local/lib/libproxychains4.dylib' could not be loaded: tried: '/usr/local/lib/libproxychains4.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need '')), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/lib/libproxychains4.dylib' (no such file), '/usr/local/lib/libproxychains4.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need ''))
dyld[5482]: tried: '/usr/local/lib/libproxychains4.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need '')), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/lib/libproxychains4.dylib' (no such file), '/usr/local/lib/libproxychains4.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need ''))
zsh: abort proxychains4 curl cip.cc
My parameters are
CFLAGS="-arch arm64" LDFLAGS="-arch arm64" ./configure
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing proxychains4 curl cip.cc after running CFLAGS="-arch arm64" LDFLAGS="-arch arm64" ./configure. Investigate the reported libproxychains4.dylib architecture mismatch; the issue is resolved when the documented build and execution path works on the reporter’s M2 system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100