| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1869.1 | Re: cam_tape.o missing RCSID from last build?!? | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Thu Oct 12 1995 17:06 | 53 |
| Date Of Receipt: 9-OCT-1995 10:40:04.86
From: SMURF::WASTED::"vandyck@cardinal.zk3.dec.com" "09-Oct-1995 1038"
To: reimers@zk3.dec.com
CC: odehelp@zk3.dec.com, reimers@zk3.dec.com
Subj: Re: cam_tape.o missing RCSID from last build?!?
How did you do your check? It looks OK to me. See below, first from the
generic kernel and then from the .o:
root@cardinal [57] what vmunix.OSF1.GENERIC |grep cam_tape
$RCSfile: cam_tape.c,v $ $Revision: 1.1.42.2 $ (DEC) $Date: 1995/10/04
18:21:36 $
root@cardinal [58] pwd
/share/inr/build/v32csupport.dsk6/v32csupportos.nightly/output
root@cardinal [59] cd usr/sys/BINARY
root@cardinal [60] ll cam_tape.o
-rw-r--r-- 1 bin bin 147943 Oct 7 03:56 cam_tape.o
root@cardinal [61] what cam_tape.o
cam_tape.o:
cam_tape.o: Read-only file system
root@cardinal [62] cp cam_tape.o /tmp
root@cardinal [64] what /tmp/cam_tape.o
/tmp/cam_tape.o:
$RCSfile: cam_tape.c,v $ $Revision: 1.1.42.2 $ (DEC) $Date: 1995/10/04
1
8:21:36 $
-Grant
| Hi,
|
| I bsubmited a change to cam_tape.c in v32csupportos.nightly on Oct 4.
| Here is the revision number:
| v32cn_mode[20] what cam_tape.c
| cam_tape.c:
| $RCSfile: cam_tape.c,v $ $Revision: 1.1.42.2 $ (DEC) $Date: 1995/10/0
4 1
| 8:21:36 $
|
| The pool built without errors on Oct 7.
| Why doesn't the object in the output directory have a revision number?
| v32cn_mode[22] pwd
| /share/inr/build/v32csupport.dsk6/v32csupportos.nightly/output/usr/sys/BINARY
| v32cn_mode[23] what cam_tape.o
| cam_tape.o:
|
| Jan Reimers
|
| 1869.2 | Re: cam_tape.o missing RCSID from last build?!? | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Thu Oct 12 1995 17:07 | 35 |
| Date Of Receipt: 9-OCT-1995 10:51:32.65
From: SMURF::WASTED::reimers "Jan T. Reimers USG 09-Oct-1995 1049"
To: "Grant Van Dyck" <vandyck@zk3.dec.com>
CC: odehelp@zk3.dec.com, reimers@DEC:.zko.wasted
Subj: Re: cam_tape.o missing RCSID from last build?!?
Grant,
Thanks for getting back to me.
Although I don't understand why you can't do a 'what' command on a
Read-only file system, file system, if I had gotten the results you did
I would have been satisfied. But I got:
v32cn_mode[31] pwd
/share/inr/build/v32csupport.dsk6/v32csupportos.nightly/output/usr/sys/BINARY
v32cn_mode[28] what cam_tape.o
cam_tape.o:
v32cn_mode[29] cp cam_tape.o /tmp
v32cn_mode[32] l cam_tape.o
-rw-r--r-- 1 bin bin 147943 Oct 7 03:56 cam_tape.o
v32cn_mode[33] l /tmp/cam*
-rw-r--r-- 1 reimers system 147943 Oct 9 10:41 /tmp/cam_tape.o
v32cn_mode[30] what /tmp/cam_tape.o
/tmp/cam_tape.o:
I got the RCSID for vmunix.OSF1.GENERIC, but I need to be able to what
the .o file to release the patch.
v32cn_mode[37] what vmunix.OSF1.GENERIC |grep cam_tape
$RCSfile: cam_tape.c,v $ $Revision: 1.1.42.2 $ (DEC) $Date: 1995/10/04 1
8:21:36 $
So what's different from what you did to what I did?
Jan
|
| 1869.3 | Re: cam_tape.o missing RCSID from last build?!? | AOSG::FILTER | Automatic Posting Software - mail to flume::puck | Thu Oct 12 1995 17:08 | 64 |
| Date Of Receipt: 9-OCT-1995 11:40:26.41
From: SMURF::ALPHA::"vandyck@cardinal.zk3.dec.com" "09-Oct-1995 1138"
To: reimers@zk3.dec.com
CC: odehelp@zk3.dec.com
Subj: Re: cam_tape.o missing RCSID from last build?!?
It is because of they're compressed objects. I copied the file to a 3.2B
system and it couldn't read it there either. When I copied cam_disk.o there I
got this:
vandyck@bubba [26] what cam_disk.o
cam_disk.o:
$RCSfile: cam_disk.c,v $ $Revision: w1.1129.7 $ (DEC) $Date:
1995/06/06 19:5?5:10 $
If you do a "file" on them on a 3.2C system you see this:
vandyck@inr [39] file cam_*.o
cam_disk.o: alpha compressed COFF executable or object module not stripped
- version 3.11-8
cam_logger.o: alpha compressed COFF executable or object module not stripped
- version 3.11-8
cam_special.o: alpha compressed COFF executable or object module not stripped
- version 3.11-8
cam_tape.o: alpha compressed COFF executable or object module not stripped
- version 3.11-8
whereas on the 3.2 system they look like datafiles:
vandyck@bubba [27] file cam*
cam_disk.o: data
cam_tape.o: data
Since they're to be installed on a 3.2C system, you need to check them on a
3.2C system.
-Grant
| I'm running V3.2
|
| Here's more info. I can do 'what' on other files.
| v32cn_mode[42] l cam_*
| -rw-r--r-- 1 bin bin 195132 Oct 7 03:55 cam_disk.o
| -rw-r--r-- 1 bin bin 4948 Oct 7 03:55 cam_logger.o
| -rw-r--r-- 1 bin bin 16266 Oct 7 03:55 cam_special.o
| -rw-r--r-- 1 bin bin 147943 Oct 7 03:56 cam_tape.o
| v32cn_mode[41] what cam_*
| cam_disk.o:
| $RCSfile: cam_disk.c,v $ $Revision: 1.1129.7 $ (DEC) $Date: 1995/06/0
6
| 19:5?5:10 $
| cam_logger.o:
| $RCSfile: cam_logger.c,v $ $Revision: 1.1.10.2 $ (DEC) $Date: 1994/0?
3/2
| 8 0:50:30 $
| cam_special.o:
| $RCSfile: cam_special.c,v $ $Revision: 1.1.11.2 $ (DEC) $Date: 1995/0
1/3
| 0 19:47:24 $
| cam_tape.o: <<<<<<<<<<<<< but no RCSID here
|