Closed Bug 4838 Opened 26 years ago Closed 25 years ago

[PP]linux build problems

Categories

(SeaMonkey :: Build Config, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 4798

People

(Reporter: dharden, Assigned: briano)

Details

I am attempting to build from the latest [8-apr-1999] source retrieved from CVS. The code is checked out properly, and the build initiates autoconf, and begins to compile. however, it gets stuck in an infinate loop with this repeated message: make[4]: Entering directory `/usr/local/src/obj-i586-pc-linux-gnu/widget/src/gtk make[4]: Leaving directory `/usr/local/src/obj-i586-pc-linux-gnu/widget/src/gtk' make[4]: Entering directory `/usr/local/src/obj-i586-pc-linux-gnu/widget/src/gtk make[4]: Leaving directory `/usr/local/src/obj-i586-pc-linux-gnu/widget/src/gtk' I have compiled mozilla several times before from cvs with no troubles. I tried removing my copy of the source, and getting a clean copy from cvs, but to no avail. I am running Debian 2.2 Potato with the latest GTK packages installed, Kernel 2.2.5, on a P5-150 w/72MB of ram. I am using client.mk (make -f mozilla/client.mk build) to drive the build.
Dave has gmake 3.77 on his machine which has a know bug. From the build instructions, "GNU make 3.77 shipped with a "$(wildcard pattern...)" bug that breaks the NSPR build. Revert to 3.76.1 until this is fixed." He turned off --enable-md and that also fixed the problem (except that now he will not get compiler-based dependencies).
Maybe we should add a check to configure.in that warns about the buggy gmake version.
is the known bug actually the problem? it worked about a week ago... i can't tell you when it broke exactly - didn't get a chance to build it throughout the week.
Summary: linux build problems → [PP]linux build problems
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 4798 ***
Status: RESOLVED → VERIFIED
Verified Duplicate
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.