Still use GCC for 64bit Linux debug builds after switch to 68 ESR

We switched to clang for our Linux builds as Mozilla did but we should still use gcc for our debug builds to have a chance of finding serious issues Mozilla missed with clang (which happened in the past).

added BugSmashFund TorBrowserTeam201909R actualpoints::0.25 component::applications/tor browser ff68-esr owner::tbb-team points::0.5 priority::medium resolution::fixed severity::normal status::closed tbb-rbm type::defect labels

Tagging with Sponsor 44

Trac:
Sponsor: N/A to Sponsor44-can

Trac:
Keywords: N/A deleted, TorBrowserTeam201909 added

Trac:
Points: N/A to 0.5

bug_31450 (https://gitweb.torproject.org/user/gk/tor-browser-build.git/commit/?h=bug_31450&id=47670953afb9026f2e49301f494d5a2faba15ec2) in my tor-browser-build repo has the fix on the build part but we need a patch for tor-browser as well (https://gitweb.torproject.org/user/gk/tor-browser.git/commit/?h=bug_31450_v3&id=56be840ce8e2c852bb040b39640db812a714a73b).

Trac:
Actualpoints: N/A to 0.25
Status: new to needs_review
Keywords: TorBrowserTeam201909 deleted, TorBrowserTeam201909R added
Cc: N/A to boklm

This looks good to me. I pushed the tor-browser commit to branch tor-browser-68.1.0esr-9.0-2 as commit 56be840ce8e2c852bb040b39640db812a714a73b, and merged the tor-browser-commit to master with commit 71eb0d2431d59ec06e4c1832df595fcd4a30cbf8.

Trac:
Status: needs_review to closed
Resolution: N/A to fixed

BugSmashFund can be used for the ESR work done so far

Trac:
Keywords: N/A deleted, BugSmashFund added

Sponsor 44 only covered PM and Team Lead work

Trac:
Sponsor: Sponsor44-can to N/A

closed

changed time estimate to 4h

added 2h of time spent

moved to tpo/applications/tor-browser#31450 (closed)