build failure with DBM 1.6 on 64 bit Solaris 8

RESOLVED FIXED

Status

NSS
Build
RESOLVED FIXED
17 years ago
17 years ago

People

(Reporter: Sonja Mirtitsch, Assigned: Sonja Mirtitsch)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

17 years ago
This is most likely a build or maybe DBM bug. Did not have any time to
investigate so far what is wrong.
Probably the include path can be set from the init scripts?

IMPORTING .... ../integration/dbm/DBM_1_6_BETA1
-----------------------------

Working on jarfile: xpheader.jar
Checking if version file exists ../../dist/public/../version

REMOVING files in '../../dist/public/../' : SunOS5.8_64_DBG.OBJ  public


Extracting jarfile 'xpheader.jar' to local directory ../../dist/public/../
unzip -o /share/builds/components/../integration/dbm/DBM_1_6_BETA1/xpheader.jar
-d ../../dist/public/..
Archive:  /share/builds/components/../integration/dbm/DBM_1_6_BETA1/xpheader.jar
  inflating: ../../dist/public/../nsres.h  
  inflating: ../../dist/public/../cdefs.h  
  inflating: ../../dist/public/../mcom_db.h  
  inflating: ../../dist/public/../ncompat.h  
  inflating: ../../dist/public/../winfile.h  
   creating: ../../dist/public/../META-INF/

Working on jarfile: mdbinary.jar
.....

../../../coreconf/nsinstall/SunOS5.8_64_DBG.OBJ/nsinstall -R -m 664
SunOS5.8_64_DBG.OBJ/libcrmf.a ../../../../dist/SunOS5.8_64_DBG.OBJ/lib
gmake[2]: Leaving directory
`/share/builds/mccrel/nss/nsstip/builds/20011029.1/booboo_Solaris8/mozilla/security/nss/lib/crmf'
cd jar; gmake libs
gmake[2]: Entering directory
`/share/builds/mccrel/nss/nsstip/builds/20011029.1/booboo_Solaris8/mozilla/security/nss/lib/jar'
cc -o SunOS5.8_64_DBG.OBJ/jarver.o -c -g -KPIC -DSVR4 -DSYSV -D__svr4 -D__svr4__
-DSOLARIS -D_REENTRANT -DSOLARIS2_8 -D_SVID_GETTOD -xarch=v9 -xs -DXP_UNIX
-DMOZILLA_CLIENT=1 -DDEBUG -UNDEBUG -DDEBUG_svbld -I/usr/dt/include
-I/usr/openwin/include -I../../../../dist/SunOS5.8_64_DBG.OBJ/include 
-I../../../../dist/public/security -I../../../../dist/private/security
-I../../../../dist/public/security -I../../../../dist/public/dbm  jarver.c
"../../../../dist/private/security/cdbhdl.h", line 43: cannot find include file:
"mcom_db.h"
"../../../../dist/private/security/cdbhdl.h", line 50: syntax error before or at: DB
"../../../../dist/private/security/cdbhdl.h", line 50: cannot recover from
previous errors
cc: acomp failed for jarver.c
gmake[2]: *** [SunOS5.8_64_DBG.OBJ/jarver.o] Error 2
gmake[2]: Leaving directory
`/share/builds/mccrel/nss/nsstip/builds/20011029.1/booboo_Solaris8/mozilla/security/nss/lib/jar'
gmake[1]: *** [libs] Error 2
gmake[1]: Leaving directory
`/share/builds/mccrel/nss/nsstip/builds/20011029.1/booboo_Solaris8/mozilla/security/nss/lib'
gmake: *** [libs] Error 2
Elapsed Time = 00:01:29
Mon 29 Oct 2001 00:16:51

Comment 1

17 years ago
Something is wrong with your init script.
Apparently you are trying to set IMPORTS to
"nspr20/v4.1.2 ../integration/dbm/DBM_1_6_BETA1"
because DBM_1_6_BETA1 is in /share/builds/integration.
This confuses the "import" script, which mistakenly
thinks that you are importing a module named ".."
with version "integration/dbm/DBM_1_6_BETA1".

If you need to import components from an area other
than /share/builds/components, you need to override
RELEASE_TREE for 'gmake import'.  You can create a
symlink /s/b/integration/nspr20/v4.1.2 pointing to
/s/b/c/nspr20/v4.1.2 so that you can simply import
both nspr20 and dbm from /s/b/integration.
Alternatively you can import nspr20 and dbm separately:
gmake import IMPORTS="nspr20/v4.1.2"
gmake import IMPORTS="dbm/DBM_1_6_BETA1" RELEASE_TREE=/share/builds/integration
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → INVALID
(Assignee)

Comment 2

17 years ago
no, I try to import both from /s/b/integration:
$Commands{gmake,parameters}  = 'IMPORTS=\'../integration/nspr20/v4.1.2
../integration/dbm/DBM_1_6_BETA1\'';

according to the log both imports go OK, but you are right, only the nspr header
files show up.
The following looks like an OK import to me - if it could not find the jar file
it should look different (I tried that, it gives me an error 2)
====
Archive:  /share/builds/components/../integration/dbm/DBM_1_6_BETA1/xpheader.jar
  inflating: ../../dist/public/../nsres.h  
  inflating: ../../dist/public/../cdefs.h  
  inflating: ../../dist/public/../mcom_db.h  
  inflating: ../../dist/public/../ncompat.h  
  inflating: ../../dist/public/../winfile.h  
   creating: ../../dist/public/../META-INF/

if I make the mistake that you think I made and attempt to import nspr from the
integration area and dbm from /s/b/c it will give me an message right in the
beginning that it is imported already, and proceed with the build:

MPORTING .... dbm/DBM_1_55_RTM
-----------------------------

Archive:  /share/builds/components/dbm/DBM_1_55_RTM/SunOS5.8_64_DBG.OBJ/mdbinary.jar

Working on jarfile: xpheader.jar
Checking if version file exists ../../dist/public/dbm/version
../../dist/public/dbm version 'DBM_1_55_RTM' already imported. Skipping...

Working on jarfile: mdbinary.jar

this build fails the same way (the version file contains the string DBM_1_6_BETA1)
I will try to work on it tomorrow, but I do not think I made the mistake you are
describing.

Status: RESOLVED → REOPENED
Resolution: INVALID → ---
(Assignee)

Comment 3

17 years ago
Oh, and I beg your forgiveness for accidentially assigning a bug of mine to you :-)
I stumbled over one of the many bugrules, the one about the default component owner
Assignee: wtc → sonja.mirtitsch
Status: REOPENED → NEW

Comment 4

17 years ago
I see what you are trying to do.  You want to import
both nspr20 and dbm from /s/b/integration.

You should override RELEASE_TREE and IMPORTS so that
the 'gmake import' command line looks like this:
gmake import IMPORTS="nspr20/v4.1.2 dbm/DBM_1_6_BETA1"
RELEASE_TREE=/share/builds/integration
(Assignee)

Comment 5

17 years ago
put Wan-Teh's suggestion in place
Assigned RELEASE_TREE = /share/builds/integration
Assigned IMPORTS = dbm/DBM_1_6_BETA1 nspr20/v4.1.2

Status: NEW → RESOLVED
Last Resolved: 17 years ago17 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.