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: <4405EB01.6020303@roguewave.com>
Date: Wed, 01 Mar 2006 11:42:09 -0700
From: Martin Sebor <sebor@roguewave.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
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>
 <4405E874.5090204@roguewave.com>
In-Reply-To: <4405E874.5090204@roguewave.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Liviu Nicoara wrote:
> 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.

If that's the case we need to put together an infrastructure that
will let us do it automatically. It's almost impossible to do it
right by hand.

Martin