From stdcxx-dev-return-3215-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Mon Apr 16 08:47:55 2007 Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 12498 invoked from network); 16 Apr 2007 08:47:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Apr 2007 08:47:55 -0000 Received: (qmail 35402 invoked by uid 500); 16 Apr 2007 08:48:02 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 35346 invoked by uid 500); 16 Apr 2007 08:48:01 -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 35335 invoked by uid 99); 16 Apr 2007 08:48:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2007 01:48:01 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of msebor@gmail.com designates 66.249.92.172 as permitted sender) Received: from [66.249.92.172] (HELO ug-out-1314.google.com) (66.249.92.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Apr 2007 01:47:55 -0700 Received: by ug-out-1314.google.com with SMTP id y2so1022695uge for ; Mon, 16 Apr 2007 01:47:33 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=JJAX11Zv7Nl6BLBJ3UwiFpI/gqRhYakJa0Mj6R1yo1axFJHyWhrPb/+0CQxdLsZbK4Xl7SHxxtx7hLdYqKab2UmfGIOwQFtv6SWaUkJEGv7KYUE8RtfUD/v4kaY5yaitN46TUJ3VtIkzmXmYjOh/Yq1042GT8rfFnmqIidrRloE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=MLyBavY/e3PIIAxD2IMy7O55DQ8Us7J5+jnyuH+sgJ9XeKb6Wc/9bP6EkXeeE3pKI3os09S/wQPfQz/BxiSIVrPMBfZlAXq5tLZeI3AH/KIbEuJJUzSNG1OxjEq/FzvMlLfbNEoc3HQv8l2bm3KzOL26EHl2ZDwZrUpjBI6bt/U= Received: by 10.82.116.15 with SMTP id o15mr7892536buc.1176713253312; Mon, 16 Apr 2007 01:47:33 -0700 (PDT) Received: from ?192.168.48.139? ( [84.201.159.18]) by mx.google.com with ESMTP id e9sm61941muf.2007.04.16.01.47.22; Mon, 16 Apr 2007 01:47:28 -0700 (PDT) Message-ID: <462337A4.7040006@roguewave.com> Date: Mon, 16 Apr 2007 02:45:24 -0600 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: stdcxx-dev@incubator.apache.org Subject: Re: Building stdcxx with EDG eccp References: <7BDB2168BEAEF14C98F1901FD2DE64386C6578@epmsa009.minsk.epam.com> <461FA2A4.1060909@roguewave.com> <7BDB2168BEAEF14C98F1901FD2DE64386C6592@epmsa009.minsk.epam.com> <462294A5.6080203@roguewave.com> In-Reply-To: <462294A5.6080203@roguewave.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Martin Sebor X-Virus-Checked: Checked by ClamAV on apache.org Martin Sebor wrote: > Farid Zaripov wrote: >>> -----Original Message----- >>> From: Martin Sebor [mailto:msebor@gmail.com] Sent: Friday, April 13, >>> 2007 6:33 PM >>> To: stdcxx-dev@incubator.apache.org >>> Cc: Martin Sebor >>> Subject: Re: Building stdcxx with EDG eccp >>> >>> Archive builds should work though (and do in my tests on Solaris, and >>> with some recent fixes, should also work on Linux, or at least be >>> very close to working). The log doesn't make much sense to me right >>> now, though. Do you have any idea what's going on there? >> >> The problem is in errors in tests at configure step. >> You can see config.h and config.log here: >> http://people.apache.org/~faridz/config.zip >> >> The most encountered error is: error #450-D: the type "long long" is >> nonstandard. >> I'll try add the option: >> ----------- >> --long_long Permit the use of long long in strict mode in dialects in >> which it is non-standard. >> ----------- > > Please don't, that's not the problem. Long long is not a standard > type (yet) and so it's not enabled. The eccp build is super-strict > on purpose, and the library must build w/o the type. The problem > is something else. Okay, now that I've actually looked at the log I see I was wrong in this case. If the C library depends on long long being defined we may have no other choice but to make eccp understand it. Sorry if I confused things. Martin