Closed
Bug 308792
Opened 21 years ago
Closed 21 years ago
No rule to make target - freebl.def
Categories
(NSS :: Build, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 307848
3.11
People
(Reporter: trupesh, Assigned: wtc)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier:
I get the below error while building trunk on AIX on 16/09/2005.
/trunk/mozilla/security/nss/lib/freebl/mpi/mp_gf2m.c
/usr/bin/gmake -j1: *** No rule to make target ../../freebl.def. Stop.
gmake[6]: *** [../../freebl.def] Error 1
gmake[6]: Leaving directory `/trunk/mozilla/obj-tinder/nss/freebl/AIX_SINGLE_SHLIB'
gmake[5]: *** [libs] Error 2
gmake[5]: Leaving directory `/trunk/mozilla/security/nss/lib/freebl'
gmake[4]: *** [libs] Error 2
gmake[4]: Leaving directory `/trunk/mozilla/security/nss/lib'
gmake[3]: *** [libs] Error 2
gmake[3]: Leaving directory `/trunk/mozilla/obj-tinder/security/manager'
gmake[2]: *** [tier_50] Error 2
gmake[2]: Leaving directory `/trunk/mozilla/obj-tinder'
gmake[1]: *** [default] Error 2
gmake[1]: Leaving directory `/trunk/mozilla/obj-tinder'
gmake: *** [build] Error 2
Reproducible: Always
Actual Results:
Build error.
Expected Results:
should get build.
Updated•21 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: other → AIX
Hardware: PC → Other
Version: unspecified → Trunk
Updated•21 years ago
|
Component: Security → Build
Product: Mozilla Application Suite → NSS
Version: Trunk → unspecified
Updated•21 years ago
|
Assignee: dveditz → wtchang
QA Contact: seamonkey → wtchang
| Assignee | ||
Comment 1•21 years ago
|
||
This is a known problem. I just checked in a fix.
Just curious: why are you building the Mozilla trunk with the
trunk of NSS? Mozilla trunk by default checks out the NSS
sources with the CVS tag NSS_CLIENT_TAG.
*** This bug has been marked as a duplicate of 307848 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Target Milestone: --- → 3.11
Version: unspecified → 3.11
You need to log in
before you can comment on or make changes to this bug.
Description
•