If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

compile of nsGREGlue.cpp using Sun C++ 5.7

RESOLVED DUPLICATE of bug 307041

Status

()

Firefox
General
RESOLVED DUPLICATE of bug 307041
12 years ago
12 years ago

People

(Reporter: Will Fiveash, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9a1) Gecko/20050831 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9a1) Gecko/20050831 Firefox/1.6a1

when trying to build the latest firefox cvs tree I see:

"/export/willf/src/mozilla/cvs/mozilla/xpcom/glue/nsGREGlue.cpp", line 472:
Error: A class with a reference member must have a user-defined constructor.
"/export/willf/src/mozilla/cvs/mozilla/xpcom/glue/nsGREGlue.cpp", line 523:
Error: Expected an expression.
"/export/willf/src/mozilla/cvs/mozilla/xpcom/glue/nsGREGlue.cpp", line 529:
Error: Use ";" to terminate statements.
3 Error(s) detected.
gmake[4]: *** [nsGREGlue.o] Error 3

I will attach the full build output.  Note this started happening when I tried
to build cvs a couple weeks ago.

Reproducible: Always
(Reporter)

Comment 1

12 years ago
Created attachment 196230 [details]
output of gmake -f client.mk
Please search for duplicates before filing; this is easily findable.

*** This bug has been marked as a duplicate of 307041 ***
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE
(Reporter)

Comment 3

12 years ago
Well, I did search for any bug that had nsGREGlue.cpp and I did not see any that
described a build breakage.  But I appreciate the tip that this is easily
findable. Next time I'll assume the bug has already been reported and I'll keep
it to myself.

Oh, I assume y'all have found the buffer overflow I discovered via libumem.
(In reply to comment #3)
> Well, I did search for any bug that had nsGREGlue.cpp and I did not see any that
> described a build breakage.  But I appreciate the tip that this is easily
> findable. Next time I'll assume the bug has already been reported and I'll keep
> it to myself.
> 
> Oh, I assume y'all have found the buffer overflow I discovered via libumem.

If "breaks build" doesn't describe a lack of compilation, I don't know what
does.  Bug reports are appreciated; please do file the buffer overflow you found
as a separate bug, too.
(Reporter)

Comment 5

12 years ago
Sorry, I was just irritated by the comment implying that I did not search for a
matching bug before I opened this bug.  I suggest that you modify your response
for duplicate bugs so as to avoid that implication.
You need to log in before you can comment on or make changes to this bug.