public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65905] Building eCos fails with clist.hxx:304:1: error: template with C linkage Date: Tue, 28 Apr 2015 08:18:00 -0000 [thread overview] Message-ID: <bug-65905-4-ODs1eAoHYT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65905-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65905 Bernd Edlinger <bernd.edlinger at hotmail dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- Oh, my fault. Accidentally I left a sym-link from arm-eabi/sys-include to ecos-test_install/include that is necessary for boot-strap, but is known to not work for building the eCos library. Although previously the error message was less cryptic.
prev parent reply other threads:[~2015-04-28 8:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-27 14:27 [Bug c++/65905] New: " bernd.edlinger at hotmail dot de 2015-04-28 8:18 ` bernd.edlinger at hotmail dot de [this message]
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=bug-65905-4-ODs1eAoHYT@http.gcc.gnu.org/bugzilla/ \ --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).