Conference hydra::axp-developer

3702.0. "Altair Computing Inc." by HYDRA::AXPDEVELOPER (Alpha Developer support) Wed Jun 04 1997 04:04

    Company Name :  Altair Computing Inc.
    Contact Name :  Dave Scarchilli
    Phone        :  
    Fax          :  
    Email        :  [email protected]
    Date/Time in :   4-JUN-1997 03:04:08
    Entered by   :  Helen Pratt
    SPE center   :  MRO

    Category     :  unix
    OS Version   :  3.2
    System H/W   :  


    Brief Description of Problem:
    -----------------------------

From:	SMTP%"[email protected]"  3-JUN-1997 17:50:55.27
To:	alpha-developer <[email protected]>
CC:	
Subj:	libcxx.so

Return-Path: [email protected]
Received: by asimov.mro.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
	Tue, 3 Jun 1997 17:50:53 -0400
Received: from pobox1.pa.dec.com by fluid.mro.dec.com (5.65v4.0/1.1.8.2/19Nov96-0448PM)
	id AA03517; Tue, 3 Jun 1997 17:50:47 -0400
Received: by pobox1.pa.dec.com; id AA02114; Tue, 3 Jun 97 14:50:44 -0700
Received: by dashub1.das.dec.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52)
	id <[email protected]>; Tue, 3 Jun 1997 17:53:02 -0400
Received: from mail12.digital.com by dashub1.das.dec.com with SMTP (Microsoft Exchange Internet Mail Connector Version 4.0.995.52)
	id MVWAR1W1; Tue, 3 Jun 1997 16:39:45 -0400
Received: from quasimooto.altair.com by mail12.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id QAA30621; Tue, 3 Jun 1997 16:34:51 -0400 (EDT)
Received: from auspex.altair.com(really [auspex.altair.com]) by quasimooto.altair.com
	via sendmail with smtp
	id <[email protected]>
	for <[email protected]>; Tue, 3 Jun 1997 15:39:48 -0400 (EDT)
	(Smail-3.2.0.92 1997-Feb-9 #1 built 1997-Apr-14)
Received: from sun48.altair.com by auspex.altair.com with smtp
	(Smail3.1.29.1) id m0wZ0Go-000Uz5C; Tue, 3 Jun 97 16:33 EDT
Received: from pc102 by sun48.altair.com (4.1/SMI-4.1)
	id AA01238; Tue, 3 Jun 97 16:33:18 EDT
Message-Id: <c=US%a=_%p=Digital%[email protected]>
From: David Scarchilli <[email protected]>
To: alpha-developer <[email protected]>
Subject: libcxx.so
Date: Tue, 3 Jun 1997 16:33:18 -0400
X-Mailer:  Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

We are currently developing a product on Digital Unix version 4.0 using
shared libs:

                        ***LIBRARY LIST SECTION***
        Name             Time-Stamp        CheckSum   Flags Version
../hm_opengl:
        libXi.so     Nov 16 02:20:49 1996 0x616d5f37     0 
        libGL.so     Nov 26 18:12:00 1996 0x9ff9bba3     0 
        libGLU.so    Nov  6 19:39:28 1996 0x57d10d40     0 
        libXext.so   Nov 16 02:10:37 1996 0xafcb84d5     0 
        libX11.so    Sep  4 15:28:07 1996 0xf31fa370     0 
        libm.so      Nov 15 20:49:59 1996 0x6888af99     0 osf.1
        libcxx.so    Nov 15 20:53:54 1996 0x966808b6     0 V4.0.1
        libexc.so    Nov 15 20:50:05 1996 0x3184247e     0 osf.1
        libc.so      Nov 15 20:49:52 1996 0xf937323b     0 osf.1


We are having a problem when customers with Digital Unix 3.2 run hm_opengl:

  % hm_opengl
  2013:hm_opengl: /sbin/loader: Fatal Error: object libcxx.so from liblist
  in hm_opengl has version "V4.0.1", which does not match the found
  object: /usr/shlib/libcxx.so (with version "")

System info: DEC Alpha 250 4/266 running DEC Unix 3.2c

I think I can solve this problem by statically linking libcxx (using .a)
instead of libcxx.so.  However, using -non_shared (cxx flag) tries to
statically link all libs and fails because there are no static libs
for OpenGL.

Is there a way to statically link ONLY libcxx ?  If not, can we distribute
libcxx.so (from Digital Unix 4.0) to customers 
with Digital Unix 3.2 ?

Do you think we will run into any other problems building on 4.0 and
running on 3.2 ?

Thanks,
Dave Scarchilli
Altair Computing Inc.
Customer code is: 905047.

I've just sent Dave the following information which should help
him determine whether he really wants to do this and if so, one possible
way in which he can progress.


> Digital UNIX provides upwards compatability, so binaries built on Digital
> UNIX V3.2 will run on Digital UNIX V4.0.  Products built on Digital
> UNIX V4.0 to run on Digital UNIX V3.2 may or may not work correctly - the
> way in which they fail may also be subtle.
> 
> To answer the second part of your query about linking with only one static
> library libcxx.a, take a look at the -no_so option on the ld man page -
> that should do what you need.


Helen.