Closed
Bug 219296
Opened 21 years ago
Closed 21 years ago
build fails on nss
Categories
(NSS :: Build, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: wliterow, Assigned: wtc)
Details
Attachments
(1 file)
9.36 KB,
text/plain
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier:
/usr/local/src/Mozilla-CVS/mozilla/security/nss
[root@walter1604 nss]# !g
gmake nss_build_all
../coreconf/ruleset.mk:211: *** missing `endef', unterminated `define'. Stop.
[root@walter1604 nss]#
Reproducible: Always
Steps to Reproduce:
1. cvs update -P ( tried this as suggested ) with success
2. gmake nss_build_all
3.
Actual Results:
../coreconf/ruleset.mk:211: *** missing `endef', unterminated `define'. Stop.
Expected Results:
expected a compile
Mandrake 9.1 2.4.21-0.13mdk #1 Fri Mar 14 15:08:06 EST 2003 i586 unknown
unknown GNU/Linux
Assignee | ||
Comment 1•21 years ago
|
||
Please attach your mozilla/security/coreconf/ruleset.mk file
(or email it to me) and post the output of this command:
cd mozilla/security/coreconf
cvs status ruleset.mk
Which build instructions are you following?
Summary: build fails on nss → build fails on nss
Reporter | ||
Comment 2•21 years ago
|
||
from
http://www.mozilla.org/directory/csdk.html
Checking Out the Source Code
Get the CVS client and set your computer up mozilla work. Read through the
instructions on using CVS. Make sure you have set your CVSROOT environment
variable and that you have successfully executed the cvs login command.
Pull the current LDAP C SDK code (which is located on the CVS trunk) using this
command:
cvs co -P DirectorySDKSourceC
Pull the code for libraries that LDAP C SDK depends on. Pull NSPR, NSS, and DBM
(used by NSS) using these commands:
cvs co -r NSPR_4_2_RELEASE mozilla/nsprpub
cvs co -r NSS_3_4_1_RTM mozilla/security/coreconf mozilla/security/nss
cvs co -r DBM_1_61_RTM mozilla/dbm mozilla/security/dbm
Alternatively, you can download stable binary releases of NSPR and NSS and drop
them into your source tree under mozilla/dist.
Obtaining Build Tools and Setting Up Your Environment
Follow these instructions to obtain the necessary build tools:
Microsoft Windows
Linux and Unix
Follow these instructions to set up your environment:
Microsoft Windows
Note that MOZCONFIG is not used for LDAP C SDK builds, so it is safe to leave
it unset.
Linix and Unix. No environment variables need to be set.
Building using autoconf (preferred method)
Build NSPR and NSS (if not using binary releases of those components) by
executing these commands:
cd mozilla/security/nss
gmake nss_build_all <<<<<<<<<<< --- fails here >>>>>>>>>>>
Reporter | ||
Comment 3•21 years ago
|
||
Assignee | ||
Comment 4•21 years ago
|
||
Comment on attachment 131531 [details]
here is the rule set that you requested
This ruleset.mk file looks okay. It is not the version in
NSS_3_4_1_RTM though. It is the version in NSS_3_3_RTM.
(The file changed in NSS_3_4_RTM.)
I can't explain why gmake complains about missing `endef',
unterminated `define'. The endef at line 213 matches the
define at line 211.
What is the output of "gmake -v"?
Reporter | ||
Comment 5•21 years ago
|
||
[root@walter1604 nss]# gmake -v nss_build_all
GNU Make 3.80
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Assignee | ||
Comment 6•21 years ago
|
||
Thanks. I just wanted to make sure that you are using
GNU make.
I am now out of ideas.
Comment 7•21 years ago
|
||
Hrm, I know that this is a strange question, but does this happen with Make
3.79? I know that a lot of people still use Make 3.79, not Make 3.80, and it's
possible that Make 3.80 is catching some bug that 3.79 doesn't catch.
-M
Reporter | ||
Comment 8•21 years ago
|
||
The problem was resolved ..turns out to be a problem with the AMD-K6(tm) 3D
processor which causes make to core on high loads in memeory
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•