Closed Bug 1141417 Opened 7 years ago Closed 7 years ago

Apitrace won't compile under gcc 4.7.3~ (the set compiler version we have been using on mozilla infra)

Categories

(Taskcluster :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jlal, Assigned: jlal)

Details

A bit of potential legacy we inherit is using the gcc-4.7.3 packages buildbot uses in our builder images... We also happen to install cmake which retriggers api trace to be built (we do not do this normally on buildbot) which reveals a bustage here:

https://treeherder.allizom.org/#/jobs?repo=b2g-inbound&revision=b79a38cf4f65

I initially thought this was some terrible TC specific issue but it looks more likely (given we are compiling this only on TC) that the new c++ features added recently are not available/on in the compiler we are using...
@mchang do we care about apitrace?
Flags: needinfo?(mchang)
I see fairly routine Bumper Bot pushes updating apitrace, so *somebody* is using it somewhere.
Just asked around gfx, nobody actively uses apitrace. Two options:

1) If it isn't too hard, can we update the apitrace version which may actually build on this version of gcc.
2) Disable building apitrace and the next person who needs it can try to fix it.
Flags: needinfo?(mchang)
fwiw- we never have built in automatically on infra until now (and I just disabled this) but I wanted to  call it out if anyone is using it (or wanted to use it)
https://hg.mozilla.org/mozilla-central/rev/f7346e74a117
Assignee: nobody → jlal
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: mozilla39 → mozilla41
Version: unspecified → Trunk
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.