Closed Bug 190794 Opened 22 years ago Closed 22 years ago

Build on Redhat Alpha Linux 7.1 fails.

Categories

(SeaMonkey :: Build Config, defect)

DEC
Linux
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: mach1, Assigned: netscape)

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux alpha; en-US; rv:1.3b) Gecko/20030111 Build Identifier: Mozilla/5.0 (X11; U; Linux alpha; en-US; rv:1.3b) Gecko/20030111 A build of the browser attempted on 26-JAN-2003 fails. A previous attempted build on 18-JAN-2003 failed in the same way. The last successful build was performed on 11-JAN-2003. I will attach an extract of the log showing the reported failure. Reproducible: Always Steps to Reproduce: 1.mkdir 26jan2003 2.cd 26jan2003 3.cvs co -f mozilla/client.mk 4.cd mozilla 5.gmake -f client.mk My .mozconfig file contains the single line: ac_add_options --enable-crypto Actual Results: See attached extract of the log. Expected Results: Completed the build successfully.
Given the time period, this may have been caused by the recombination of the layout & content shared libs. Do you see the same problem if you try doing a --disable-debug build or --enable-debugger-info-modules=^layout,^content ?
I tried a build with each of the two options you mentioned with similar results. I just added each option in turn to .mozconfig and re-issued the gmake command, but I did not do a complete new download of the source from scratch. Both builds failed on the build of libgklayout.so.
Since those are configure flags, you would have to at least re-run configure for them to take effect. I would suggest doing a distclean first and building from scratch with those flags.
I have attempted a new build from scratch with the additional options. The build failed in the same manner as before.
I tried building 1.3b on alpha (Compaq/Red Hat 7.2) and libgklayout.so linked fine.
I did hit this bug trying to do a debug build with current CVS trunk, but adding --disable-debug didn't help. I'm trying to figure out what was different between the 1.3b build and current trunk that broke it. 1.3b (RPM options, worked) --prefix=/usr --libdir=/usr/lib --enable-optimize --disable-debug --with-default-mozilla-five-home=/usrl/lib/mozilla-1.3b --enable-strip --disable-tests --disable-short-wchar --enable-nspr-autoconf --enable-crypto --without-system-nspr --with-system-zlib --disable-xft --mandir=/usr/share/man trunk (died trying to link libgklayout.so) --disable-mailnews --disable-ldap --disable-freetype2 --disable-xprint --disable-jsd --disable-postscript --disable-composer --disable-installer --disable-mathml --disable-accessibility --disable-dtd-debug --disable-debug --enable-strip marking NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
adding --disable-tests --enable-optimize to the trunk build "fixed" it. Is there any reason that optimization would help here?
just as a general pointer, recombining layout and content libs will require more swap space than before. mach1: how much swap space do you have allocated?
the Alpha I'm compiling on has 256MB RAM and 512 MB swap. I'll watch swap usage next time it links (I think I noticed my i686 build get up to ~200MB total memory usage).
My Alpha also has 256MB of RAM and a 534MB swap partition.
my optimized debug build died just as the unoptimized non-debug build. ld occupied 80-90MB of memory and free swap space didn't drop below 440MB.
I grabbed the most recent binutils release (2.13.2.1) and with that version, libgklayout.so linked properly and Mozilla seems to work fine. http://sources.redhat.com/binutils/ Red Hat 7.2's standard binutils is version 2.11.90.0.8-14 I filed a bug with Compaq/HP for this issue as it does not seem to be Mozilla's fault: http://alpha.crl.dec.com/bugzilla/show_bug.cgi?id=37
FYI: the binutils-2.11.93.0.2-11 SRPM from Red Hat 7.3 / x86 rebuilt for Alpha also works fine here
Well, after some googling, I cannot find the abiword fix referenced by http://alpha.crl.dec.com/bugzilla/show_bug.cgi?id=37 but http://sources.redhat.com/ml/binutils/2002-11/msg00177.html seems to imply that it's a binutils bug of some sort which matches Andrew's tests. Marking invalid.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: