mozilla-central windows l10n builds failing with sdk error

RESOLVED FIXED

Status

Release Engineering
General Automation
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: bhearsum, Assigned: glandium)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
configure: error: You are targeting Windows version 0x06020000, but your SDK only supports up to version 0x06010000. Install and use an updated SDK, or target a lower version using --with-windows-version. Alternatively, try running the Windows SDK Configuration Tool and selecting a newer SDK. See https://developer.mozilla.org/En/Windows_SDK_versions for more details on fixing this.

Probably will be fixed when bug 784848 lands.
(Assignee)

Comment 1

5 years ago
Created attachment 717028 [details] [diff] [review]
Work around l10n repack bustage with --enable-metro

Since we're not really building anything for firefox during repacks, the sdk version doesn't matter, so we can force to use the older one despite --enable-metro as a workaround.
Attachment #717028 - Flags: review?(jmathies)
(Assignee)

Updated

5 years ago
Assignee: nobody → mh+mozilla

Comment 2

5 years ago
Comment on attachment 717028 [details] [diff] [review]
Work around l10n repack bustage with --enable-metro

I'll approve this but I really don't know much about l10n builds, so I'll just assume mh knows, which I'm sure he does.
Attachment #717028 - Flags: review?(jmathies) → review+
Comment on attachment 717028 [details] [diff] [review]
Work around l10n repack bustage with --enable-metro

since jim was leery about l10n, I'll r+ as releng that this is indeed sane enough to do.
Attachment #717028 - Flags: review+
(Assignee)

Comment 4

5 years ago
https://hg.mozilla.org/mozilla-central/rev/e162098b76d9
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED

Comment 5

5 years ago
When could we expect new builds of l10n win32 now that it is fixed ?
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.