Closed Bug 134176 Opened 24 years ago Closed 24 years ago

0.9.9 rpm source building: gcc-3.0.4 coredumps

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: peter, Assigned: netscape)

References

()

Details

[...] morkObject.h:129: warning: by `virtual nsresult morkObject::CutStrongRef(nsIMdbEnv*)' nsMorkFactory.cpp make[4]: *** [libs] Segmentation fault (core dumped) make[3]: *** [libs] Error 2 make[2]: *** [libs] Error 2 make[1]: *** [tier_9] Error 2 make: *** [default] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.79681 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.79681 (%build) [root@peter i386]#
did you just do rpm --rebuild? could you try with gcc-2.xx? this doesn't look like a Mozilla bug.
Assignee: asa → seawood
Component: Browser-General → Build Config
QA Contact: doronr → granrose
Could you provide a bit more information here? This doesn't look like a Mozilla bug. From that snippet, it looks like it's make, not gcc that's coredumping. What version of make are you using?
2 Andrew: I did rpm --rebuild as usual. I did it with egcs-2.91 on mozillas 0.9.1 through 0.9.5, gcc-2.96 on mozilla 0.9.6 gcc 3.0.3 on mozilla 0.9.7. The current gcc-3.0.4 and make-2.79.1 seem to compile kernel nicely.
2 Christopher: what kind of information would you like? I provide as I use to do: kernel-2.4.17, glibc-2.2.4, XFree86-4.0.3, make-2.79.1 I realize that hell knows what happen on gcc and near (make, etc.) at redhat'ish systems. Sorry, I'm just wondering at response level. Thank you, I'm going to take gcc-2.95.3 at last and keep silence.
I'm not sure gcc-2.xx will help. It's just the most notale difference between your build and most other people. The Makefile (and relevant configuration files) are not going to be that different (some not different at all). You might also try out a source tar.bz2 (instead of SRPM). The config is slightly different.
As far as the more information request, the following would be helpful: a full build log from a clean tree including configure config.log config/autoconf.mk
Marking invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
verified invalid.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.