[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9444 [Tor bundles/installation]: Create deterministic TorBrowserBundles with Pluggable Transports
#9444: Create deterministic TorBrowserBundles with Pluggable Transports
------------------------------------------+--------------------------
Reporter: bastik | Owner: erinn
Type: task | Status: needs_review
Priority: normal | Milestone:
Component: Tor bundles/installation | Version:
Resolution: | Keywords: flashproxy
Actual Points: | Parent ID:
Points: |
------------------------------------------+--------------------------
Comment (by dcf):
Now there are bundles for linux and mac.
* https://people.torproject.org/~dcf/pt-bundle/3.0-beta-1-pt20131114/
These come from commit 80cb9490726e76768b8dddde6e1d82b9b2ecf3d2.
I had to apply the `pwd` workaround from #10030.
In the 2.x series of PT bundles, compiled Python modules such as
Crypto/Cipher/_AES.so were fat binaries containing i386 and x86_64
architectures, just because that was the default behavior of the native
compiler. Now using the cross compiler, they come out as i386 only. I
found that trying to import such a module caused a runtime error using the
default 64-bit Python 2.7 on OS X 10.9. The commit log for
80cb9490726e76768b8dddde6e1d82b9b2ecf3d2 has more information. What I did
was add the environment variables
{{{
VERSIONER_PYTHON_VERSION=2.6
VERSIONER_PYTHON_PREFER_32_BIT=yes
}}}
to the same wrapper script used to do the #10030 workaround.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9444#comment:16>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs