[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:	USG buildhelp questions/answers

Moderator:	SMURF::FILTER

Created:	Mon Apr 26 1993
Last Modified:	Mon Jan 20 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2763
Total number of notes:	5802

1439.0. "New shared library and Ship_as_upd.." by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Thu Apr 27 1995 17:39

Date Of Receipt: 	27-APR-1995 12:55:23.30
From: 	SMURF::ALPHA::sandeep "Sandeep Shah USG  27-Apr-1995 1253"
To: 	buildhelp@DEC:.zko.alpha
CC: 	sandeep@DEC:.zko.alpha (sandeep shah)
Subj: 	New shared library and Ship_as_upd..

Hi,

I don't know if this is the right place to ask this, but I have a question
about the inventory and what does the following mean?

	3       ./usr/shlib/.upd..libc.so       OSFBASE400
	0       ./usr/shlib/libc.so     Ship_as_upd

I want to add a new shared library and I was not sure if I need to supply
the .upd..libxxx.so (and why and how).

Thanks a lot.

Sandeep Shah

T.R Title User Personal
Name Date Lines

1439.1 Re: New shared library and Ship_as_upd.. AOSG::FILTER Automatic Posting Software - mail to flume::puck Thu Apr 27 1995 17:40 30

T.R	Title	User	Personal Name	Date	Lines
1439.1	Re: New shared library and Ship_as_upd..	AOSG::FILTER	Automatic Posting Software - mail to flume::puck	`Thu Apr 27 1995 17:40`	30
	Date Of Receipt: 27-APR-1995 13:14:06.51 From: SMURF::FLUME::overman "James C. Overman" To: buildhelp sandeep CC: Subj: Re: New shared library and Ship_as_upd.. Sandeep The makefile for libc.so will make both ./usr/shlib/libc.so and ./usr/shlib/.upd..libc.so. They are the same file just installed to the output tree with different names. The ./usr/shlib/.upd..libc.so version ships in the product in the OSFBASE400 subset and is moved into the ./usr/shlib/libc.so name during the install. The ./usr/shlib/libc.so that is in the output tree is used for bos installs. To answer the question of ' does a new shared library need both standard name and a .upd.. name?' depends on if the new shared library would be in use when the system is in standalone mode, or during either installation or update install. If the new shared library will not be active then you don't need both filenames. If the new shared library will be active then both filenames will be needed and that is done in the Makefile. Regards, James

Date Of Receipt: 	27-APR-1995 13:14:06.51
From: 	SMURF::FLUME::overman "James C. Overman"
To: 	buildhelp sandeep
CC: 	
Subj: 	Re:  New shared library and Ship_as_upd..

Sandeep

The makefile for libc.so will make both ./usr/shlib/libc.so
and ./usr/shlib/.upd..libc.so.  They are the same file just
installed to the output tree with different names.  The 
 ./usr/shlib/.upd..libc.so version ships in the product
in the OSFBASE400 subset and is moved into the 
 ./usr/shlib/libc.so name during the install.  The 
 ./usr/shlib/libc.so that is in the output tree is used
for bos installs.

To answer the question of ' does a new shared library need
both standard name and a .upd.. name?' depends on if the
new shared library would be in use when the system is in
standalone mode, or during either installation or update
install.  If the new shared library will not be active then
you don't need both filenames.  If the new shared library 
will be active then both filenames will be needed and
that is done in the Makefile.

	Regards,
		James