Closed Bug 403337 Opened 19 years ago Closed 17 years ago

JS 1.7.0 won't compile with gcc 3.X -- jsapi.c is the culprit

Categories

(Core :: JavaScript Engine, defect)

x86
Windows XP
defect
Not set
major

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: shanti, Unassigned)

References

Details

Attachments

(1 obsolete file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 Build Identifier: SpiderMonkey 1.7.0 If you get a bunch of "initializer element is not constant" in jsapi.c, it's because the JSStdName struct now has a JSClass* element that doesn't seem to resolve at compile time. Reproducible: Always Steps to Reproduce: gcc.exe -c -fexceptions -I . -idirafter js/ -D _Windows -D XP_WIN -D _HAS_INT64 -oobj\gcc\jsapi.o js/jsapi.c Actual Results: jsapi.c: initializer element is not constant
Attached file Fix (obsolete) —
Blocks: 401087
Comment on attachment 288157 [details] Fix Please submit this fix as a patch against the original (via CVS) instead of attaching the entire file.
Attachment #288157 - Attachment is obsolete: true
Shanti: Can you submit a cvs diff -u of that patch as said in Comment 2?
We used to work fine with GCC 3.x when this jsapi.c code was introduced, IIRC. Anyway, we and pretty much the rest of the world are using GCC 4.x. I don't think we want this patch. At a glance,something seems wrong with the particular version you're using. /be
I think this bug is obsolete now.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: