[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hpux-cxx-dev
Subject:    RE: CXX-DEV: Migrating form aCC A.01.21 on HP-UX B.10.20 to aCC A
From:       TSmith () maninvestmentproducts ! com
Date:       2002-07-30 14:35:46
[Download RAW message or body]

Thank you Tim and Dennis for your input. 
I was tempted with Tim's idea, but it seems to me that this will relies on luck \
rather than design. Although I do think it has a reasonable chance of success, I \
don't think it's suitable for a production system as Dennis  rightly says.

As a result of my linking problems, it is inevitable that the 3rd party 
library will be upgraded to one for HP-UX 11 as I'm not the only one who 
uses it. I'm just going to have to wait for it.

TTFN Tony
 
Man Investment Products Ltd

-----Original Message-----
From: Dennis Handly [mailto:dhandly@cup.hp.com]
Sent: 30 July 2002 11:58
To: cxx-dev@cxx.cup.hp.com
Subject: Re: CXX-DEV: Migrating form aCC A.01.21 on HP-UX B.10.20 to aCC
A.03.33 on HP- UX B.11.11


> When linking my application on an HP-UX 11.11 machine using aCC A.03.33, >ld: \
> Unsatisfied symbols: __ConstructArray(void *,unsigned int,unsigned int,void \
> (*)(),void (*)()) __DestructArray(void *,unsigned int,unsigned int,void (*)()) \
> (code) operator new[](unsigned int) (code)

This is the size_t roll when going to 11.x:
http://docs.hp.com/hpux/onlinedocs/dev/aCC/a_03_33/RelNote.html
Potential Binary Incompatibility of Objects Built with HP-UX 10.10, 10.20
aC++

> it is unlikely that I will have access to an appropriate version of this
> library in the short term.

I assume you will finally get a version?

> Is there a library that will give me some sort backward compatibility? 
No, we say you can NOT mix and match 10.x with 11.x.
You must recompile everything if you recompile/relink anything.

> Can I safely program my way round this (and how)?
TTFN Tony

What Tim suggests is not supported.
You will have to determine if you want to go with Tim's kludge and be
unsupported or wait until you get a new version of the lib.
If you are not putting your application into production, you might be able
to gamble with Tim's kludge.

> From: "Tim Frye" <timothy_frye@hp.com>
> You could write your own version of __ConstructArray() and
__DestructArray() 
> using "unsigned int" type.

> There may be bigger issues than simply the link message because of aCC
> complexities.
-Tim

The bigger issue is libc compatibility.  The size_t roll hides that all
from you.  I.e. the 10.x headers only go with the 10.x libc and may cause
problems with a 11.x libc.
 _________________________________________________________________
 To leave this mailing list, send mail to majordomo@cxx.cup.hp.com
    with the message UNSUBSCRIBE cxx-dev
 _________________________________________________________________


**********************************************************************
Any information in this communication which is confidential must not
be disclosed to others without our consent. Such consent is not required
where the information is publicly available and intended for onward
distribution. If the information is confidential and if you are not the
intended recipient, you are not authorised to and must not disclose,
copy, distribute, or retain this message or any part of it. You are
requested to return this message to the sender immediately.

Due to the electronic nature of e-mail, there is a risk that the
information contained in this message has been modified. 
Consequently Man Investment Products can accept no responsibility or
liability as to the completeness or accuracy of the information.

Visit us at: www.maninvestmentproducts.com

**********************************************************************

 _________________________________________________________________
 To leave this mailing list, send mail to majordomo@cxx.cup.hp.com
    with the message UNSUBSCRIBE cxx-dev
 _________________________________________________________________


[prev in list] [next in list] [prev in thread] [next in thread]