Add nasm in MinGW32/64 and the L10n for Windows 2012 opt 32/64
Categories
(Firefox Build System :: Toolchains, enhancement)
Tracking
(firefox67 affected)
Tracking | Status | |
---|---|---|
firefox67 | --- | affected |
People
(Reporter: achronop, Assigned: TD-Linux)
References
Details
Attachments
(2 files, 1 obsolete file)
In order to enable ASM dav1d build on windows we are missing MinGW32/64 and the L10n for Windows 2012 opt 32/64 as described in [1].
Assignee | ||
Comment 1•6 years ago
|
||
I think at least l10n should be fixed by a rebase.
Reporter | ||
Comment 2•6 years ago
|
||
In [1] is a latest try. I don't see a l10s build running at all. I haven't done anything differently. In any case if those runs have been removed only MinGW runs are the remaining failure.
[1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=ad81a2977c43088285c812290cce5c099091b93b
Assignee | ||
Comment 3•6 years ago
|
||
Reporter | ||
Comment 4•6 years ago
|
||
This try run includes the patch in comment 3 on the top of the patches that enable ASM dav1d builds on windows from Bug 1521062.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=2d4698421d6a19067560bcb193d8005c46e12689
Assignee | ||
Comment 5•6 years ago
|
||
This one doesn't inherit the common mozconfig.nasm file.
Updated•6 years ago
|
Assignee | ||
Comment 7•6 years ago
|
||
Assignee | ||
Comment 8•6 years ago
|
||
I made an alternate attachment. I had misunderstood mingw as using elf for .o, but it uses COFF, and nasm only supports cv8 debug info for that. I have no idea how the yasm manages to work, it's either stuffing dwarf in COFF or not being built at all for mingw.
Assignee | ||
Updated•6 years ago
|
Comment 9•6 years ago
|
||
bugherder |
Reporter | ||
Comment 10•6 years ago
|
||
There is a second patch in the queue that needs to be landed. We can close it then.
Updated•6 years ago
|
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
bugherder |
Comment 13•6 years ago
|
||
(In reply to Alex Chronopoulos [:achronop] from comment #10)
There is a second patch in the queue that needs to be landed. We can close it then.
Looks like both landed now, right? Can we resolve this?
Reporter | ||
Comment 14•6 years ago
|
||
Yeah, everything is there now, thank you very much.
Reporter | ||
Updated•6 years ago
|
Description
•