Closed
Bug 348735
Opened 19 years ago
Closed 19 years ago
Support building js jshell with gcov
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: bc, Unassigned)
References
()
Details
Attachments
(2 files)
876 bytes,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
556 bytes,
patch
|
Details | Diff | Splinter Review |
building the js shell on linux with gcc fails when compiling jscpucfg since it not built with CFLAGS or LDFLAGS.
Reporter | ||
Comment 1•19 years ago
|
||
add CFLAGS and LDFLAGS to jscpucfg's rule.
Attachment #233792 -
Flags: review?(mrbkap)
Updated•19 years ago
|
Attachment #233792 -
Flags: review?(mrbkap) → review+
Reporter | ||
Comment 2•19 years ago
|
||
Checking in Makefile.ref;
/cvsroot/mozilla/js/src/Makefile.ref,v <-- Makefile.ref
new revision: 3.42; previous revision: 3.41
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 3•19 years ago
|
||
jscpucfg is a build-host helper, it needs HOST_CFLAGS and HOST_LDFLAGS. You do not want to measure its code coverage. Cc'ing build gurus who can correct me if I'm wrong.
/be
Reporter | ||
Comment 4•19 years ago
|
||
I don't know what I was smoking this weekend, but I can no longer reproduce the problem I was having. set XCFLAGS=--coverage and js shell builds fine for me on the trunk without any change to Makefile.ref. This bug is really invalid.
Reporter | ||
Updated•19 years ago
|
Flags: in-testsuite-
Reporter | ||
Comment 5•19 years ago
|
||
(In reply to comment #2)
> Checking in Makefile.ref;
> /cvsroot/mozilla/js/src/Makefile.ref,v <-- Makefile.ref
> new revision: 3.42; previous revision: 3.41
>
This patch was BS and should not have been committed.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 6•19 years ago
|
||
Checking in Makefile.ref;
/cvsroot/mozilla/js/src/Makefile.ref,v <-- Makefile.ref
new revision: 3.43; previous revision: 3.42
Reporter | ||
Updated•19 years ago
|
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•