For aarch64 platform, I have built "TinyProxy" from source.

Open
#568 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
10/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux
Domain
backend

Research direction

The report describes a successful TinyProxy build on aarch64 using the project’s installation steps, but does not request a change or identify a file to edit. Read the installation instructions linked in the issue and check whether the project wants aarch64 build information documented; done would require a concrete documentation change request.

Written by the indexing model from the issue text.

Description

needs-information

Steps

Following STEPS were used for the building and installation:


$ wget https://github.com/tinyproxy/tinyproxy/releases/download/1.10.0/tinyproxy-1.10.0.tar.gz 

$ tar -zxvf tinyproxy-1.10.0.tar.gz && cd tinyproxy-1.10.0 

$ ./configure 

$ make 

$ make install 

Outcome

To validate that the build was successful, we ran file command for tinyproxy binary inside ./src/

$ file tinyproxy 

tinyproxy: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=f183fceccc0e8f3f45f2d384ddd24fd26daea72d, for GNU/Linux 3.7.0, with debug_info, not stripped 

All this information is also added to Software Ecosystem Dashboard for Arm (https://www.arm.com/developer-hub/ecosystem-dashboard/).

Dominant language
C
Stars
6.1k
Forks
768
Avg merge
15d 3h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from tinyproxy/tinyproxy

All issues in tinyproxy/tinyproxy

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.