public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pda at freeshell dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/58075] New: Unable to build go on ia64-hp-hpux11.31 Date: Sun, 04 Aug 2013 02:42:00 -0000 [thread overview] Message-ID: <bug-58075-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58075 Bug ID: 58075 Summary: Unable to build go on ia64-hp-hpux11.31 Product: gcc Version: 4.7.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: pda at freeshell dot org Excuse the lack of further detail, but the message looks pretty self-explanatory. .../gcc-4.7.3/libgo/runtime/proc.c:114:4: error: #error unknown case for SETCONTEXT_CLOBBERS_TLS Is this just a case of go not being ready for this platform yet?
next reply other threads:[~2013-08-04 2:42 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-04 2:42 pda at freeshell dot org [this message] 2013-08-04 18:44 ` [Bug go/58075] " ian at airs dot com 2013-08-12 23:48 ` pda at freeshell dot org 2013-08-13 0:00 ` ian at airs dot com 2015-02-03 20:04 ` ian at airs dot com
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-58075-4@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).