[tor-bugs] #12631 [Applications/Tor Browser]: Tor Browser for ARM architecture
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Jan 8 10:02:25 UTC 2019
#12631: Tor Browser for ARM architecture
--------------------------------------+------------------------
Reporter: mttp | Owner: (none)
Type: project | Status: new
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: tbb-rbm | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+------------------------
Comment (by gk):
Replying to [comment:20 JeremyRand]:
> Updated my rbm descriptors for ARM to work with ESR 60.
https://notabug.org/JeremyRand/tor-browser-build/src/armhf-esr60 (the
armhf-esr60 branch). Docs still at
https://wiki.raptorcs.com/wiki/Porting/Tor_Browser . One noteworthy thing
is that, due to what is probably
https://bugzilla.mozilla.org/show_bug.cgi?id=1452128 , I needed to upgrade
to gcc 7.3.0 / binutils 2.29.1. I don't know if that's a dealbreaker for
Tor (and I haven't carefully tested whether the upgrade breaks anything on
non-ARM platforms). Can anyone from Tor comment on whether the specific
gcc / binutils versions used by Tor Browser were chosen for a particular
reason, and whether upgrading them would be considered if it's the most
straightforward way to get ARM to work?
Thanks for working on the ARM port, really appreciated! Updating GCC to
7.3.0 is probably no problem. Binutils 2.29.1 is trickier, though, as with
binutils 2.26 we have a hard to fix reproducibility issue on Windows which
currently prevents upgrading (see: #26148). We could think about using
2.29.1 just for ARM as a workaround (in case there are no reproducibility
issues involved here and the Mozilla bug does not get fixed meanwhile)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12631#comment:21>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list