[tor-bugs] #17379 [Applications/Tor Browser]: Using the same build process in Tor Browser and Tor Messenger

[Tor Bug Tracker & Wiki]

#17379: Using the same build process in Tor Browser and Tor Messenger
--------------------------------------+-----------------------
 Reporter:  boklm                     |          Owner:  boklm
     Type:  task                      |         Status:  new
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  tbb-gitian                |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------

Comment (by mcs):

 Kathy and I successfully ran `make alpha_nightly` on an Ubuntu 14.04 LTS
 system. Here is some quick feedback:

 a) It would be nice to have log output that provided a "high level" view
 of progress (e.g., Building tor for Linux64, Building pluggable transports
 for Linux64, Building firefox for Linux64....) The old gitian-based build
 system does not do this very well either; maybe we should have two log
 files? Or something that is easy to grep for within the make output.

 b) How can we reduce the number of languages that we produce packages for?
 Doing that is useful when creating test builds since it speeds up
 packaging time.

 c) The resulting Linux build runs, but the OSX one does not (we did not
 yet try to run the Windows build). On OSX, libevent seems to be missing
 and tor.real has a dependency on this path:
  /var/tmp/dist/libevent/lib/libevent-2.0.5.dylib
 In current OSX builds (e.g., TB 7.0a1), tor.real has a dependency on:
  @executable_path/libevent-2.0.5.dylib

 After we copied libevent from TB 7.0a1 to the /var/tmp/... path, we got
 further: tor.real started up and completed the bootstrap phase but it
 exited immediately after that point:
  [notice] Owning controller connection has closed -- exiting now.

 We do not know why tor thinks the connection has closed (maybe the browser
 is closing the control port connection or maybe it is not). Is this a
 known problem?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17379#comment:12>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online