>> In respect to a problem with 'ld' not reading an archive: has anyone heard
>> of an 'ld' problem with systems which upgraded in place from 1.3 to 2.1?
>> That is, a re-install was NOT done.
>
As it turned out, the problem was NOT with 'ld' but with the configuration of
Shadow's 'makefile'... that is, for some reason it did not execute 'ar' prior
to 'ranlib'. Manually running 'ar' solved the problem. If I understood 'make',
'ar' and 'ranlib' better this would have been obvious.
Since there *are* issues with 'ld' under OSF/1 v. 2.1 I've summarized the
following
responses.
Thanks to everyone who replied.
-Philip
From:
+---------------------------+tm Paul E. Rockwell
| | | | | | | | UNIX Sales Support Consultant
| d | i | g | i | t | a | l | Digital Equipment Corporation
| | | | | | | | 500 Enterprise Drive
+---------------------------+ Rocky Hill, CT 06067
Internet: rockwell_at_rch.dec.com Phone: (203)258-5022
Easynet: koodie::rockwell DTN: 320-5022
>I've seen a problem with upgrading from 1.3 to anything 2.x if you had the
>optional Development Enhancements installed from 1.3. The problem is as
>follows:
>
>1 - upgrade 1.3 to 2.0
>2 - realize that you didn't de-install the CMPDEVENH130 subsets *after* you
> did this upgrade. You then do a setld -d of this subset.
>3 - Now you find some funny stuff going on with the linker.
>
>What happened is that, unbeknownst to you, the installation process for the
>CMPDEVENH130 subsets squirreled away a copy of the original 1.3 linker. When
>you deinstalled the subset under 2.x, you blew away the 2.x linker with the
>1.3 linker. The best way to check this is to compare the ld that's currently
>installed on the system with what's supposed to be installed (look at the
>OSFBASE2xx.inv file and get the file size, date and checksum out of that).
>
>If it isn't the right one, then you can extract the original off the
>OSF/1 release CD. (you can cat | uncompress | tar xvf -
{path-of-ld-from-the-.inv-file}).
>
From:
-------------------------------------------------------------------------
Marco Luchini Internet : m.luchini_at_ic.ac.uk
>Yes indeed. This seems to happen quite often and is tied (I believe) to
>the existence of the Developmente Enhancements subsets. This has it's
>own linker and screws up the install.
>
>Look in /usr/lib/cmplrs/cc. If ld has a different date from all the
>others you've got the 1.3 ld which will not work. Grab it off the CD.
>Check /usr/.smdb./*.inv for which subset it comes off (I don't have an
>alpha handy now to check).
>
From my neighbour:
- David L. Cairns E-mail: cairns_at_upei.ca
>Did you try to telete/rename libshadow.a before the make? If there was a
>'stub' or an existing library it is possible that OSF can not read the format.
From: "(Steve Postlethwaite +44 (0)1992 501414)" <steve_at_sql.com>
>I've seen the compiler/linker issue some pretty obscure error messages if
there
>isn't enough space in /tmp (or $TMPDIR) for temporary files. Worth checking.
>
>
>Steve
Thanks again,
-Philip
--
Philip M. Howard, Systems Administrator |howard_at_peinet.pe.ca
PEINet Inc. |tel: 902-892-7346
PO Box 3126, Charlottetown, |fax: 902-368-2446
Prince Edward Island, CANADA C1A 7N9 |http://www.peinet.pe.ca/
Received on Tue Feb 21 1995 - 11:40:09 NZDT