[omniORB] omniORB, solaris10x86 and CORBA::LongDouble

[Harri Pasanen]

I'm not sure if this is relevant to this, but from memory here, (a bit vague):

If I recall, at one or two points there is a test if long double is 12 bytes 
or 16 bytes based on if on x86.  This resulted in a wrong interpretation if 
the hosting os was x86_64, but the target build was 32 bit.

Solution was to give the host and target as explicit paremeters to configure 
script.

-Harri

On Tuesday 04 April 2006 16:37, Duncan Grisby wrote:
> On Tuesday 4 April, "Roloff, Craig A" wrote:
> > We use the configure script.  It shows:
> >
> > checking for long double... yes
> > checking size of long double... 16
>
> So you do indeed have long double...
>
> > Yet the preprocessor shows:
> >
> > ../../../bin/omniidl -bcxx -Wba -p../../../../src/lib/omniORB -Wbdebug
> > -v -nf -P -WbF -ComniORB4 ../../../../idl/corbaidl.idl
> > omniidl: Importing back-end 'cxx'
> > omniidl: 'cxx' imported from
> > '../../../../src/lib/omniORB/omniidl_be/cxx/__init__.pyc'
> > omniidl: Preprocessing '../../../../idl/corbaidl.idl' with
> > '/project/aero/swdev/perf/omni407/hp11i/lib/omnicpp -lang-c++ -undef
> > -D__OMNIIDL__=0x2420 -DHAS_LongLong -D__OMNIIDL_CXX__
> > "../../../../idl/corbaidl.idl"'
> >
> > We've tried to trace this problem before without any luck.  Can you
> > suggest where to look?
>
> The defines come from idlpython.cc in the IdlPyPlatformDefines function,
> where it just sets the defines according to what's set when that file is
> compiled. Something somewhere is preventing HAS_LongDouble from being
> set, or is undefining it once it's set. I wonder if Python.h is doing
> something that prevents SIZEOF_LONGDOUBLE being right. All I can suggest
> you do is to add some things to the files being #included to trace why
> HAS_LongDouble is not set when idlpython.cc is compiled.
>
> Cheers,
>
> Duncan.


Privileged or confidential information may be contained in this message.  If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Trema does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Trema does not accept liability for any damage sustained as a result of viruses.  Statements in this message or attachments that do not relate to the business of Trema are neither given nor endorsed by the company or its directors. A list of Trema's directors is available on our web site: www.trema.com