Closed
Bug 293592
Opened 20 years ago
Closed 14 years ago
Unsatisfied symbol while linking firefox on HP-UX
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: stefan_blobner, Unassigned)
Details
(Whiteboard: [CLOSEME 2011-2-25])
User-Agent: Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.8a6) Gecko/20050119
Build Identifier: Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.7.7) Gecko/20050510 Firefox/1.0.3
When statically linking firefox-bin on HP-UX:
/usr/ccs/bin/ld: Unsatisfied symbols:
static DOMCSSDeclarationImpl::operator new(unsigned long) (first referenced
in ../../dist/lib/components/libgklayout.a(nsCSSStyleRule.o)) (code)
This is caused by a missing implementation in
./content/html/style/src/nsCSSStyleRule.cpp, line #893:
void* operator new(size_t size) CPP_THROW_NEW;
possibly, the CPP_THROW_NEW is undefined on HP-UX...
we managed to fix it to get the build to work by modifying the line to:
void* operator new(size_t size) CPP_THROW_NEW { throw bad_alloc(); return 0;}
but this might not be really the final solution that you want in the generic code.
the same issue happens in the Mozilla 1.8.x build. only the location there is
./layout/style/nsCSSStyleRule.cpp, line #915.
Reproducible: Always
Steps to Reproduce:
happens while building on HP-UX
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
| Reporter | ||
Comment 2•19 years ago
|
||
The issue is still reproducable on Firefox 1.5b1, only the location of the issues has been moved to ./layout/style/nsCSSStyleRule.cpp, line 926.
Comment 3•19 years ago
|
||
I see the same failure with Firefox 1.5 RC2 also. /usr/ccs/bin/ld: Unsatisfied symbols: static DOMCSSDeclarationImpl::operator new(unsigned long) (first referenced in ../../dist/lib/components/libgklayout.a(nsCSSStyleRule.o)) (code) make[4]: *** [firefox-bin] Error 1 make[4]: *** Deleting file `firefox-bin'
| Reporter | ||
Comment 4•18 years ago
|
||
this issue still exists in FireFox 2.0 Beta 2.
Comment 5•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
Comment 6•14 years ago
|
||
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
| Assignee | ||
Updated•6 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•