[tor-bugs] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

Tor Bug Tracker & Wiki blackhole at torproject.org
Wed Mar 7 17:19:05 UTC 2018


#16472: Upgrade Binutils to 2.25+ for Tor Browser builds
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  tbb-
                                                 |  team
     Type:  task                                 |         Status:
                                                 |  needs_review
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201803R,      |  Actual Points:
  boklm201803                                    |
Parent ID:  #12968                               |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by cypherpunks):

 Replying to [comment:45 gk]:
 > Replying to [comment:44 boklm]:
 > > Replying to [comment:43 cypherpunks]:
 > > > bump mingw-w64 ;)
 > >
 > > Building firefox with `master` from mingw-w64 fails with:
 > > {{{
 > > i686-w64-mingw32-widl:
 /var/tmp/build/mingw-w64-b633824ecafd/mingw-w64-tools/widl/src/typetree.h:274:
 type_alias_get_aliasee: Assertion `type_is_alias(type)' failed.
 > > Aborted
 > > Makefile:109: recipe for target 'typelib_done' failed
 > > }}}
 It can be something recent and close to binutils 2.30 release date, not
 necessary `master`.
 > Yeah, we should not do that right now,
 What about Nightlies?
 > at least not until we found the issue why the crash is happening
 Do you mean https://sourceware.org/git/gitweb.cgi?p=binutils-
 gdb.git;a=commit;h=9d9c67b06c1bf4c4550e3de0eb575c2bfbe96df9 ?
 > (fwiw I notified Jacek about it, see the stylo bug on Mozilla's bug
 tracker as a patch from him is causing that breakage).
 Where?
 > I think picking the latest stable that works
 2.29.1 ?
 > and filing an upstream bug (making sure it is still unfixed) seems like
 a good idea to me.
 Hrm...

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


More information about the tor-bugs mailing list