Return-Path: Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org Received: (qmail 46702 invoked from network); 18 Jul 2007 19:31:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jul 2007 19:31:41 -0000 Received: (qmail 20006 invoked by uid 500); 18 Jul 2007 19:31:27 -0000 Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org Received: (qmail 19983 invoked by uid 500); 18 Jul 2007 19:31:27 -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 19937 invoked by uid 99); 18 Jul 2007 19:31:27 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2007 12:31:27 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jul 2007 12:31:24 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CE7C37141EB for ; Wed, 18 Jul 2007 12:31:04 -0700 (PDT) Message-ID: <31144259.1184787064842.JavaMail.jira@brutus> Date: Wed, 18 Jul 2007 12:31:04 -0700 (PDT) From: "Andrew Black (JIRA)" To: stdcxx-dev@incubator.apache.org Subject: [jira] Resolved: (STDCXX-489) [Intel C++ 10.0/Linux] BUILDMODE=narrow has no effect In-Reply-To: <6374193.1184782924583.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/STDCXX-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Black resolved STDCXX-489. --------------------------------- Resolution: Invalid Greetings Mark. I'm closing this issue as 'Invalid', as the cause of the problem is your environment. Unlike most other compilers, the Intel compiler doesn't have a command line switch to control whether the generated executables are 32 or 64 bit. Rather, there are two separate executables, one 32 bit, and one 64 bit. (The only other compilers I can think of with this behavior are Visual Studio and the Intel Compiler for Windows.) To produce a 32 bit executable with the Intel compiler, you will need to use the correct iccvars.sh to set up your environment. This quirk of the Intel compiler has caused problems for me also. If you have an Intel Premier account, https://premier.intel.com/premier/IssueDetail.aspx?IssueID=420157 was a support request I filed asking for assistance on this subject. --Andrew Black > [Intel C++ 10.0/Linux] BUILDMODE=narrow has no effect > ----------------------------------------------------- > > Key: STDCXX-489 > URL: https://issues.apache.org/jira/browse/STDCXX-489 > Project: C++ Standard Library > Issue Type: Bug > Components: Configuration > Affects Versions: 4.2 > Environment: Intel C++ 10 on Linux > Reporter: Mark Brown > > Configuring stdcxx for 32-bits using BUILDMODE=pthreads,archive,optimized,narrow on x86_64 I see the system architecture is "LP64 little endian" instead of "ILP32 little endian." It looks like the "narrow" in BUILDMODE has no effect, kind of like "wide" had no effect in bug STDCXX-470. > $ nice make BUILDDIR=/home/mbrown/stdcxx-icc-10.0-12s BUILDMODE=pthreads,archive,optimized,narrow CONFIG=icc.config > creating BUILDDIR=/home/mbrown/stdcxx-icc-10.0-12s > generating /home/mbrown/stdcxx-icc-10.0-12s/makefile.in from /home/mbrown/stdcxx/etc/config/icc.config > make[1]: Entering directory `/home/mbrown/stdcxx-icc-10.0-12s' > make[2]: Entering directory `/home/mbrown/stdcxx-icc-10.0-12s/include' > make config > make[3]: Entering directory `/home/mbrown/stdcxx-icc-10.0-12s/include' > configuring stdcxx 4.2.0 for icc-10.0 on linux-2.6.18-1.2798.fc6-x86_64 > checking if the compiler is sane ok (invoked with icc) > checking if the linker is sane ok (invoked with icc) > checking system architecture LP64 little endian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.