public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mpeck@akamai.com To: gcc-gnats@gcc.gnu.org Subject: preprocessor/8798: #include <locale> is including /usr/bin/locale instead of /usr/local/include/c++/3.2.1/locale Date: Tue, 03 Dec 2002 08:16:00 -0000 [thread overview] Message-ID: <20021203160828.8829.qmail@sources.redhat.com> (raw) >Number: 8798 >Category: preprocessor >Synopsis: #include <locale> is including /usr/bin/locale instead of /usr/local/include/c++/3.2.1/locale >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Tue Dec 03 08:16:04 PST 2002 >Closed-Date: >Last-Modified: >Originator: mpeck@akamai.com >Release: gcc version 3.2.1 >Organization: >Environment: Debian 3.0 (woody) based OS with RedHat Kernel >Description: A #include <iostream> leads to /usr/local/include/c++/3.2.1/bits/istream.tcc:37 doing a #include <locale>, which then issues a failure on /usr/bin/locale:10:184, and several others. I don't understand where /usr/bin/locale is coming from. I tried changing istream.tcc to #include </usr/local/include/c++/3.2.1/locale>, but same results, and changing the "<>" to double quotes also got same result. Here's the output from the compiler: ====================================== Computing dependencies for mapDispatcher/pingState.cc In file included from /usr/local/include/c++/3.2.1/bits/istream.tcc:37, from /usr/local/include/c++/3.2.1/istream:297, from /usr/local/include/c++/3.2.1/iostream:46, from /d0/20021203-0635/akamai/common/include/Mapper/Dispatcher/pingState.h:8, from /d0/20021203-0635/akamai/mapDispatcher/pingState.cc:9: /usr/bin/locale:10:184: missing terminating ' character /usr/bin/locale:28:1089: missing terminating ' character /usr/bin/locale:43:3674: missing terminating ' character /usr/bin/locale:58:132: missing terminating ' character /usr/bin/locale:66:604: missing terminating ' character /usr/bin/locale:67:544: missing terminating " character /usr/bin/locale:1:409: possible start of unterminated string literal In file included from /d0/20021203-0635/akamai/common/include/Mapper/Dispatcher/TPS_Types.h:6, from /d0/20021203-0635/akamai/common/include/Mapper/Dispatcher/pingState.h:67, from /d0/20021203-0635/akamai/mapDispatcher/pingState.cc:9: /d0/20021203-0635/akamai/common/include/akamai/utils/ak_icmp.h:224:7: warning: no newline at end of file ERROR: could not compute dependencies mapDispatcher/pingState.cc make-3.79.1-aka-2[1]: *** [/d0/20021203-0635/akamai/mapDispatcher/pingState.cc.d] Error 1 Here's the full compiler version: root@esiejtest3:/usr/local/include/c++/3.2.1# gcc -v Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs Configured with: /usr/local/src/gcc-3.2.1/configure --prefix=/usr/local --with-gun-as --with-gnu-ld Thread model: posix gcc version 3.2.1 root@esiejtest3:/usr/local/include/c++/3.2.1# gcc --version gcc (GCC) 3.2.1 Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. root@esiejtest3:/usr/local/include/c++/3.2.1# >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-12-03 16:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021203160828.8829.qmail@sources.redhat.com \ --to=mpeck@akamai.com \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).