Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4405E874.5090204@roguewave.com>
Date: Wed, 01 Mar 2006 11:31:16 -0700
From: Liviu Nicoara <nicoara@roguewave.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: Problem with num_put on zOS
References: 
 <4FA4B7B3231C5D459E7BAD020213A94202948FD6@bco-exchange.bco.roguewave.com>
In-Reply-To: 
 <4FA4B7B3231C5D459E7BAD020213A94202948FD6@bco-exchange.bco.roguewave.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

What Martin means by configuring the library is the first leg of
"make"-ing the library, where the GNU makefiles direct the execution of
 the config tests and the creation the config.h header. You could see
for yourself how this goes by building the library on a UNIX w/o RCB
(i.e. using GNU makefiles).

I am pretty sure I know from Tim or John that the reason why we're using
a hardcoded config header is that zOS is missing a shell and the
required utilities.

Liviu

Nicole Willson wrote:
> As far as I know the library was configured for zOS using sp6 code and that
> was simply adapted to sp7.  I guess I don't know what you mean by
> configuring the library.  I thought that was what I was doing by changing
> the rwc_std_11d.h file.
> 
> Nicole Willson
> Consulting Engineer
> Rogue Wave Software, Inc.
> A Division of Quovadx
> 303-545-3210
> 
> 
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com] 
> Sent: Wednesday, March 01, 2006 10:29 AM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: Problem with num_put on zOS
> 
> Martin Sebor wrote:
> 
>>Nicole Willson wrote:
>>
>>
>>>As to how I configured the library: I did not.  Someone set this up long
>>>before I got here and left the company.  I've only made what tweaks were
>>>needed to the makefiles to get everything to build.  And now I've tweaked
>>>the rwc_std_11d.h file, to define the NO_COLLAPSE macros listed 
>>>below.  I am
>>>not aware of anything more that is required to configure the library 
>>>outside
>>>of RCB and ccd files.
>>
>>
>>It is critical that you reconfigure the library when you switch
>>environments, especially when you are moving from one OS to a
>>another that is likely to be quite different. I don't know much
>>about z/OS but from what I've heard it's nothing like anything
>>else out there. A compiler on such an OS is also likely to be
>>different than even the same compiler on another OS (just think
>>about IBM XLC++ on AIX and Linux and the differences between
>>the two).
>>
>>If you'd configure the library you'll almost certainly wind up
> 
> 
> This should be "If you don't reconfigure the library..."
> 
> Martin
> 
> 
>>with a misconfigured product. You might get it to compile and
>>link, and if you're lucky you might even get programs to run
>>but you will run a huge risk of not adapting the library to
>>some obscure and otherwise hard to detect bugs or quirks.
>>
>>Martin
> 
>