./mach build gives "[Error 193] %1 is not a valid Win32 application"
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
People
(Reporter: abbGZcvu_bugzilla.mozilla.org, Unassigned)
Details
Attachments
(1 file)
Comment 2•12 years ago
|
||
Comment 5•11 years ago
|
||
Comment 6•11 years ago
|
||
Updated•7 years ago
|
Updated•3 years ago
|
Comment 7•2 years ago
|
||
Hello, I had the same error and found the solution. The problem is in the bootstrap.py file in the which function definition. This program is expecting Mercurial executable to be named hg.exe, but mine is named hg.bat. Confirmed by running this command in my powershell: (Get-Command hg).Path
I'm not sure if this is caused by an update to Mercurial, but I have a simple solution that would allow compatibility with both naming conventions.
Can I claim this bug so I can push a fix?
Comment 8•2 years ago
|
||
I should also add that I am running Windows 11 and the ticket's platform is marked as Windows 8. Just wanted to put that out there in case someone wanted to update the platform to include Windows 11, because this bug definitely occurs on Windows 11.
I have a NEEDSINFO request on this but I do not know what I am being asked to do. Please clarify and create a new one if needed.
Comment 10•2 years ago
|
||
Sorry, I am new to this Bugzilla platform. I'd like to be assigned to this ticket
| Reporter | ||
Comment 11•2 years ago
|
||
I don't work on FF; I just reported the issue. I'm sure there's a doc somewhere that explain what to do. You can probably just submit a patch.
Comment 12•2 years ago
|
||
Ah ok, my bad. Yeah I'll probably just submit it. It's a very simple fix
Comment 13•2 years ago
|
||
When bootstrapping, the which function is used to find the Mercurial executable (hg is the executable name). On Windows, it is possible that Mercurial is installed with extension .bat, which this script does not account for.
Description
•