Closed
Bug 40939
Opened 25 years ago
Closed 24 years ago
nsXPIDLString.cpp compile problem with on Linux/ia64
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
RESOLVED
INVALID
mozilla0.8.1
People
(Reporter: jim_nance, Assigned: scc)
References
Details
I have a problem building nsXPIDLString.cpp on an IA64 machine.
I am not sure if its a source code problem or a configure
script problem. The compile dies with the error:
In file included from
/home/users/jnance/mbuild/mozilla/xpcom/ds/nsXPIDLString.cpp:25:
/home/users/jnance/mbuild/mozilla/xpcom/ds/nsXPIDLString.h: In function `PRBool
operator== (const PRUnichar *, const nsXPIDLString &)':
/home/users/jnance/mbuild/mozilla/xpcom/ds/nsXPIDLString.h:201: static_cast from
`const nsXPIDLString' to `const PRUnichar *'
and several other warnings about casts. If I go into the
config-defs.h file generated by configure an undef HAVE_CPP_NEW_CASTS
then the build works. I do not know if the source is wrong
or if the configure script should detect this problem.
*** Bug 40938 has been marked as a duplicate of this bug. ***
Comment 2•25 years ago
|
||
From testing and asking around this seems to be a bug in the compiler. Can't
really work around it.
Moving all current open XPCOM and XPCOM Registry bugs to rayw since dp is on
sabbatical. rayw is now default assignee for these components.
Assignee: dp → rayw
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 4•25 years ago
|
||
=> scc
Assignee: rayw → scc
Status: ASSIGNED → NEW
Target Milestone: --- → M20
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Updated•24 years ago
|
QA Contact: leger → kandrot
Assignee | ||
Updated•24 years ago
|
Component: XPCOM → String
Target Milestone: --- → mozilla0.9
Assignee | ||
Comment 5•24 years ago
|
||
So what's the status of this, guys? Compiler bug (suggested by blizzard)? Is
this something we can fix? Is it still troubling you? If I don't get tickled
back that this is still a problem and something we can reasonably fix, I'm going
to mark it closed somehow (either INVALID, or WONTFIX, or something).
I no longer have access to an IA64 machine to test on, so I dont really know
if this is still a problem or not. Its fine with me if you mark it as INVALID.
I suspect its been fixed.
Assignee | ||
Updated•24 years ago
|
Target Milestone: mozilla0.9 → mozilla0.8.1
Assignee | ||
Comment 7•24 years ago
|
||
as suggested, marking INVALID. Thanks, Jim.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Updated•4 years ago
|
Component: String → XPCOM
You need to log in
before you can comment on or make changes to this bug.
Description
•