public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wanderer at rsu dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20537] New: GCC install libstdc++ headers in wrong dir Date: Fri, 18 Mar 2005 19:24:00 -0000 [thread overview] Message-ID: <20050318192437.20537.wanderer@rsu.ru> (raw) Current GCC mainline (4.1.0 20050318) install libstdc++ headers at FreeBSD 5.3 in <gcc-dir>/include/c++/const/ dir instead <gcc-dir>/include/c++/4.1.0/ I think problem related to last GCC version generation changes. I build and install without this problem GCC 4.1.0 20050313 Vladimir -- Summary: GCC install libstdc++ headers in wrong dir Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: wanderer at rsu dot ru CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i386-unknown-freebsd5.3 GCC host triplet: i386-unknown-freebsd5.3 GCC target triplet: i386-unknown-freebsd5.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20537
next reply other threads:[~2005-03-18 19:24 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-18 19:24 wanderer at rsu dot ru [this message] 2005-03-18 19:30 ` [Bug bootstrap/20537] [4.1 Regression] " pinskia at gcc dot gnu dot org 2005-03-18 19:31 ` pinskia at gcc dot gnu dot org 2005-03-19 16:39 ` pinskia at gcc dot gnu dot org 2005-03-21 17:57 ` pinskia at gcc dot gnu dot org
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=20050318192437.20537.wanderer@rsu.ru \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).