Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 63531 invoked from network); 1 Mar 2006 19:27:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 1 Mar 2006 19:27:59 -0000 Received: (qmail 99285 invoked by uid 500); 1 Mar 2006 19:28:38 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 99244 invoked by uid 500); 1 Mar 2006 19:28:37 -0000 Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stdcxx-dev@incubator.apache.org Delivered-To: mailing list stdcxx-dev@incubator.apache.org Received: (qmail 99196 invoked by uid 99); 1 Mar 2006 19:28:37 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2006 11:28:37 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [208.30.140.160] (HELO moroha.quovadx.com) (208.30.140.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2006 11:28:36 -0800 Received: from bco-exchange.bco.roguewave.com (bco-exchange.bco.roguewave.com [172.19.31.48]) by moroha.quovadx.com (8.13.4/8.13.4) with ESMTP id k21JR5Lg026596 for ; Wed, 1 Mar 2006 19:27:06 GMT Received: from [10.70.3.113] (10.70.3.113 [10.70.3.113]) by bco-exchange.bco.roguewave.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id F5YGRRHX; Wed, 1 Mar 2006 12:27:33 -0700 Message-ID: <4405F6D7.6090805@roguewave.com> Date: Wed, 01 Mar 2006 12:32:39 -0700 From: Martin Sebor User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 X-Accept-Language: en-us, en 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> <4405EB01.6020303@roguewave.com> In-Reply-To: <4405EB01.6020303@roguewave.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Luckily, GNU make and a bunch of other handy tools are available for z/OS. Here's a helpful article: http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg245992.html?OpenDocument GNU make itself as well as a bunch of other useful stuff that will make your experience on z/OS more tolerable (i.e., UNIX-like) can be downloaded from here: http://www-03.ibm.com/servers/eserver/zseries/zos/unix/bpxa1ty1.html#opensrc Martin Martin Sebor wrote: > 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