rofl0r / rofl0r/microsocks

Android ARM compile

Open
#8 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
2.2k
Forks
353
Avg merge
1h 4m
Merged PRs (30d)
1

Description

Hello.

I'm trying to cross-compile microsocks for android 5.1.1 with arm-linux-musleabi-gcc (from musl-cross-make). Compile is okay, but have issues with execute on my device.

Firstly i got error:
error: only position independent executables (PIE) are supported.

And i added

CFLAGS += -fPIE
LDFLAGS += -Wl,--dynamic-linker=/system/bin/linker -fPIE -pie

to make parametres.

After this changes and re-compiled i got another error on device:

WARNING: linker: Unsupported flags DT_FLAGS_1=0x8000000
WARNING: linker: ./microsocks has text relocations. This is wasting memory and prevents security hardening. Please fix.
CANNOT LINK EXECUTABLE: cannot locate symbol "__errno_location" referenced by "./microsocks"...

And now i dont know what to do.
Can you help me with it? Please

Also i want to compile all dynamic libraries to binary, i dont know how to do it too...
Sorry my english is bad, and i just only learning now about sources and compile, googled not give me any success. Thanks you for any help.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No project files or tests are identified. Start by reviewing the Android ARM make invocation, CFLAGS, LDFLAGS, and the linker diagnostics; reproduce the build and device execution failure, then establish whether microsocks can run on Android 5.1.1 without the reported PIE, text-relocation, and __errno_location errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
build-system, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.