Closed Bug 216403 Opened 22 years ago Closed 20 years ago

Unable to start Mozilla after compile

Categories

(MailNews Core :: Backend, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: partha, Assigned: sspitzer)

Details

(Whiteboard: INVALID)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701 Build Identifier: Mozilla 1.5 alpha When I start mozilla from where I compiled it I get the following message: /home/downloads/mozilla/source/mozilla/dist/bin/mozilla-bin: relocation error: /home/downloads/mozilla/source/mozilla/dist/bin/components/libmail.so: undefined symbol: _ZN18nsMsgContentPolicyC1Ev Reproducible: Always Steps to Reproduce: 1. Download alpha source 2. Compile after generating .mozconfig 3. start from dist/bin location Actual Results: I got the above detailed error Expected Results: mozilla should start.
Do you compiled it in the same location as an older build (untar the source in the same directory) ? doesn't block development
Severity: blocker → critical
libmail.so is not part of Seamonkey. Did you try to build Thunderbird? If you switch build options like that, you need to % gmake -f client.mk distclean before you rebuild.
Whiteboard: INVALID
I deleted the whole directory and started from scratch. I then recreated .mozconfig and pulled the source from CVS with the following option: mk_add_options MOZ_CO_DATE="16 Aug 2003 17:04 PST" The build went fine, but I had the same problem. I noticed that since the problem was related to libmail (which I found in ../mailnews/build), I re-edited my .mozconfig and commented out the following line: ac_add_options --enable-static-mail Then, I did a distclean and rebuilt mozilla. Then the build went fine and I was able to run mozilla. I would say the problem maybe with the static-mail option? In anycase, saying that "Nobody else has this problem but you" is hardly helpful and not very conducive to people wanting to get involved. Thanks, Partha
--enable-static-mail turns on part of the thunderbird build process. I'm not sure of the intended effect of turning it on manually, but it's possible you got it. If you want a standalone mail client, build thunderbird outright.
Product: MailNews → Core
resolving INVALID FYI: relevant build options are completely different now
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.