#26323: Build 32bit Linux bundles on 64bit systems -------------------------------------------+------------------------------- Reporter: gk | Owner: tbb-team Type: task | Status: | needs_revision Priority: Very High | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: tbb-rbm, TorBrowserTeam201903 | Actual Points: Parent ID: #26468 | Points: Reviewer: | Sponsor: -------------------------------------------+-------------------------------
Comment (by boklm): Replying to [comment:15 gk]: > Replying to [comment:14 boklm]: > > There are two patches for review in branch `bug_26323_v7`: > > https://gitweb.torproject.org/user/boklm/tor-browser- build.git/commit/?h=bug_26323_v7&id=676f75ecb97484368b340ee5d355aa422c2b0a7c > > `tor` compilation for nightly builds breaks in this case with > {{{ > configure: error: TOR_RUST_TARGET must be specified when cross-compiling with Rust enabled. > }}} Oh, I forgot to test the nightly target. > > > I think a possible improvement we can do after this, is to share the gcc and rust builds between linux32 and linux64. > > Hm, what is missing here? In particular, I wonder what the issue with GCC is as the build script at least should be the same (modulo the different hash in the bundle name that stems from somewhere else). Yes, GCC is built exactly in the same way in both cases, the only difference is the list of packages installed in the containers, and the `dpkg --add-architecture i386` we only run in the i686 case (which are causing the hash in the filename to differ). -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26323#comment:19> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs