Open Bug 1525066 Opened 5 years ago Updated 2 years ago

Please provide a mozilla-build version that works on aarch64/arm64 Windows

Categories

(Firefox Build System :: General, enhancement, P3)

enhancement

Tracking

(Not tracked)

People

(Reporter: Gijs, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: in-triage)

I don't know how feasible this would be, especially since it would involve producing a separate mozilla-build--I presume we don't want most people building with 32-bit tools. Ryan, how hard do you think it would be to produce a separate mostly-32-bit mozilla-build installation?

Flags: needinfo?(ryanvm)

As Gijs noted in his blog post, most of the packages we ship have 32-bit versions, so it's plausible to have some sort of "lite" 32-bit package where we ship what we can and omit the rest.

A rough idea offhand of what would need to be done:

  • Finding 32-bit versions of whatever we can
  • Updating the packaging script to create either a 32-bit or 64-bit version and deciding what to package accordingly
  • Updating the installer to allow 32-bit installation where appropriate (requires Win7+ 64-bit at the moment)

At least offhand, those are the main things I can think of. They certainly seem doable assuming someone has the time to invest. That person isn't me, regretfully.

Flags: needinfo?(ryanvm)

We talked about this in triage our team meeting and we weren't sure how many people would actually use this package and weather it was worth the significant engineering work to make this happen and maintain the package going forward.

Keywords: in-triage
Priority: -- → P3

(In reply to Kim Moir [:kmoir] ET from comment #3)

We talked about this in triage our team meeting and we weren't sure how many people would actually use this package and weather it was worth the significant engineering work to make this happen and maintain the package going forward.

Not just Gijs and frontend folks, but me on the fuzzing team are also hitting this and some form of ARM64 Windows environment work may be on Mozilla's radar for the upcoming months. Without this environment I'm actually unsure how some of our testing can take place.

Would this be enough justification?

(Bumping to major, but not changing priority)

Severity: normal → major
Flags: needinfo?(kmoir)
Depends on: 1453980
Priority: P3 → P2
Flags: needinfo?(kmoir)
Keywords: in-triage
Flags: needinfo?(kmoir)

I don't know exactly where this should be in our priorities, but I don't think we can move anything we're working on in the short term. This is enough work that we'd have to defer something in order to make it happen given our current staffing and expertise.

Flags: needinfo?(kmoir)
Priority: P2 → P3

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --
You need to log in before you can comment on or make changes to this bug.