| Return-Path: [email protected]
Received: from fluid by damage.mro.dec.com (5.65v3.2/1.1.10.5/14Oct96-0412PM)
id AA23231; Wed, 15 Jan 1997 17:17:29 -0500
Received: from mail12.digital.com by fluid.mro.dec.com;
(5.65v3.2/1.1.8.2/19Nov96-0448PM)
id AA16374; Wed, 15 Jan 1997 17:17:20 -0500
Received: from mail.mti.cdc.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV)
id PAA27658; Wed, 15 Jan 1997 15:10:39 -0500 (EST)
Message-Id: <[email protected]>
Received: from gwpc19 (gwpc19.mti.cdc.com) by mail.mti.cdc.com with SMTP
(1.39.111.2/16.2) id AA229289016; Wed, 15 Jan 1997 14:10:16 -0600
Date: Wed, 15 Jan 1997 14:10:16 -0600
X-Sender: [email protected]
X-Mailer: Windows Eudora Light Version 1.5.2
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: [email protected]
From: Steve Sellars <[email protected]>
Subject: Re: Strip problems in V3.0
Cc: [email protected]
John:
[Re: Log number 1997-3026]
Here is a link sequence that produces a shared library and the strip command
error message:
ld -x -g -shared -expect_unresolved "*" -o libscsa.so globref.o
-L/int/m23/build/csa/lib -lmath -ltable -lutil -lskt -linst -lrpc -lvc
-lcfg -lvc -lmscd -ldlow -lnls -lsys -lzunx -llow -lvc -lnls -lsys
-ligen -ligec -lzunx -llow -lc -lm
DU1(smdw-23)11% cd lib
DU1(smdw-23)13% strip libscsa.so
strip: Info: shared object is not stripped
We had a similar problem on SGI Unix where they provide a -f option for
stripping shared libraries.
Here is the compiler command used to compile the object files:
cc -std1 -O0 -c
Again, this happens on Digital Unix Version 3.0, but not on 3.2G.
|
| Return-Path: john
Received: from localhost by damage.mro.dec.com (5.65v3.2/1.1.10.5/14Oct96-0412PM)
id AA23773; Thu, 16 Jan 1997 15:57:45 -0500
Message-Id: <[email protected]>
To: [email protected]
Cc: john
Subject: Re: Strip problems in V3.0
In-Reply-To: Your message of "Thu, 16 Jan 97 12:34:11 CST."
<[email protected]>
Date: Thu, 16 Jan 97 15:57:44 -0500
From: john
X-Mts: smtp
Steve,
Always in damage control! What I meant about support, is that bugs and issues
such as these which are fixed in later versions, as which seems to be the case
here, get no bandwidth with engineering. If its field test, latest rev., or one
back, we tend to have the ability to ask for patches when we can supply a test
case of the issue. Sorry for the confusion. I will continue to check the
database for specific strip issues reported by others, I fear, that I may not
dig anything up. I will keep you updated.
regards,
john
Alpha Developer Support
|