Closed
Bug 72154
Opened 23 years ago
Closed 23 years ago
Can't build JS Shell with CygWin 1.1.8
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: pschwartau, Assigned: rogerl)
References
Details
Attachments
(1 file)
Our Makfile.ref uses the uname command to determine what the OS is. On my WinNT box, my CygWin B20 shell gives this result: [/]uname WINNT Our makefile then looks for a config file like "WINNT4.0.mk" in js/src/config. Everything is fine. But my new CygWin 1.1.8 shell gives this result for uname: [/]uname CYGWIN_NT-4.0 We have to update our make system to handle this so that CygWin 1.1.8 users can build the standalone JS shell ...
I'm pretty sure that your cygwin b20 setup was using netscape's hacked uname. Afaik, cygwin's uname has always returned CYGWIN_XX-YY. See nsprpub/configure.in or nsprpub/config/arch.mk for cygwin uname detection logic.
Summary: Can't build JS Shell with CygWin 1.1.8 → Can't build JS Shell with CygWin 1.1.8
Reporter | ||
Comment 3•23 years ago
|
||
This patch does the trick for me on WinNT. I can now build the JS Shell with either CygWin 1.1.8 or Cygwin B20, no problem. Thank you for doing this !!!
Comment 4•23 years ago
|
||
a= asa@mozilla.org for checkin to the trunk. (on behalf of drivers)
Patch has been checked in.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•