| Date Of Receipt: 7-OCT-1996 12:32:04.20
From: FLUME::"[email protected]" "07-Oct-1996 1229"
To: [email protected]
CC: [email protected], [email protected], [email protected],
[email protected], [email protected]
Subj: Re: Problems with tcr1supportos.nightly
The cscope databases get pushed to nightly when the nightly gets pushed, which
is when it's successful, which this hasn't been for a while. For your
convenience, I pushed the failed build's cscope database to nightly.
I looked for the two undefined symbols and found they were both in:
kernel/kern/lockinfo.c - ONLY.
So far this pool has only taken in these files:
./kernel/rm/ccomsub.c,v 1.1.17.2
./kernel/rm/ccomsub.h,v 1.1.16.2
./kernel/io/drd/drd_drv.c,v 1.1.7.2
./kernel/rm/rm_error.c,v 1.1.8.2
./kernel/rm/rm_kern.c,v 1.1.17.2
Hope this helps a little in your analysis.
-Grant
| Hi,
|
| Sorry, but I was out at a customer last week, and apparently noone has done
| anything else with this...
|
| I talked with Andy Duane who mentioned a problem with ld that can cause
| "hundreds" of "branch relocation out of range" errors if there is a multiply
| defined, or undefined, symbol. In looking at the logs for the failed build
| on Sept 25, I noticed that there are two undefineds at the beginning of the
| hard errors. When I build GENERIC in my sandbox, I do not have this problem.
| The only error message I get is in rm_spur where it does complain about the
| branch relocation being out of range, but successfully builds a GENERIC kerne
l
| with the trampoline code.
|
| Here is the beginning of tcr1supportos.nightly/Logs/Error.summary:
|
| kernel.bld.log:4569:Error: Undefined:
| kernel.bld.log:4932:Error: Undefined:
| kernel.bld.log:4449:cnx_hab_cfg.o: branch relocation out-of-range, bad object
| file produced, can't branch from 0xfffffc000064b8b4 to 0xfffffc000023f66c
| kernel.bld.log:4572:mcs_asalloc.o: branch relocation out-of-range, bad object
| file produced, can't branch from 0xfffffc0000663184 to 0xfffffc00002450fc
| .
| .
| .
|
| I have no idea where the undefineds are coming from. Could someone figure
| out why we get them? Again, I do NOT get these errors when I build the
| kernel, so I suspect that a header file, or something, is being left off in
| the build environment.
|
| Also, tcr1supportos.nightly does not appear to have any cscope information.
| Could someone please fix this?
|
| Thank-you,
|
| Rob Marshall
| USEG
--
-Grant
|