public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: setzersn@gmx.de To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: c++/8319: warnings out of system headers Date: Thu, 24 Oct 2002 01:26:00 -0000 [thread overview] Message-ID: <20021024082601.23054.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8319; it has been noted by GNATS. From: setzersn@gmx.de To: gcc-gnats@gcc.gnu.org Cc: Subject: c++/8319: warnings out of system headers Date: 23 Oct 2002 08:39:17 -0000 >Number: 8319 >Category: c++ >Synopsis: warnings out of system headers >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Oct 23 01:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Sebastian Setzer >Release: unknown-1.0 >Organization: >Environment: gcc -v Reading specs from ...sparc-sun-solaris2.5.1/3.2/specs Configured with: .../configure --prefix=... --program-suffix=-3.2 --with-gnu-as --with-as=...bin/as --with-gnu-ld --with-ld=...bin/ld --enable-threads --enable-version-specific-runtime-libs --enable-languages=ada,c,c++ Thread model: posix gcc version 3.2 >Description: The problem described below disappears, if I DON'T set the environment variables. But now I get warnings out of system-headers (which I shouldn't, should I ?) ../3.2/include/c++/bits/stl_threads.h: In instantiation of `__gthread_mutex_t std::_Swap_lock_struct<0>::_S_swap_lock': ../3.2/include/c++/bits/stl_threads.h:122: instantiated from here ../3.2/include/c++/bits/stl_threads.h:115: warning: aggregate has a partly bracketed initializer ../3.2/include/c++/bits/stl_threads.h:115: warning: aggregate has a partly bracketed initializer > When I want to compile a simple Program which does an > #include <iostream> > I get errors like this one: > ------------------------------------------------------- > In file included from .../3.2/include/c++/iosfwd:45, > from .../3.2/include/c++/ios:44, > from .../3.2/include/c++/ostream:45, > from .../3.2/include/c++/iostream:45, > from read.cpp:1: > .../3.2/include/c++/bits/stringfwd.h:49: > template > with C linkage > ------------------------------------------------------- > where ... is a quite long path. > I've set the following environment variables: > > set gcc32dir=/projects/tmp/setzersn/gcc3/install_02 > setenv GCC_EXEC_PREFIX ${gcc32dir}/lib/gcc-lib/sparc-sun-solaris2.5.1/3.$ > setenv LIBRARY_PATH ${gcc32dir}/lib/gcc-lib/sparc-sun-solaris2.5.1/3.2 > setenv C_INCLUDE_PATH ${gcc32dir}/lib/gcc-lib/sparc-sun-solaris2.5.1/3.$ > setenv CPLUS_INCLUDE_PATH ${gcc32dir}/lib/gcc-lib/sparc-sun-solaris2.5.1/3.$ > set path = (${gcc32dir}/bin $path) > >How-To-Repeat: Compile a program with #include <iostream> (On Solaris ?) >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-10-24 8:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-24 1:26 setzersn [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-23 1:46 setzersn
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=20021024082601.23054.qmail@sources.redhat.com \ --to=setzersn@gmx.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).