public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/36545] Type _uleb128_t doesn't defined properly in /gcc/unwind-dw2.c Date: Mon, 11 Aug 2008 01:08:00 -0000 [thread overview] Message-ID: <20080811010726.8633.qmail@sourceware.org> (raw) In-Reply-To: <bug-36545-15391@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2008-08-11 01:07 ------- How did you configure GCC and how did you invoke make? -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING GCC host triplet|i686-pc-mingw32 | GCC target triplet| |i686-pc-mingw32/ http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36545
next prev parent reply other threads:[~2008-08-11 1:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-06-16 1:41 [Bug bootstrap/36545] New: " andry at inbox dot ru 2008-08-11 1:08 ` pinskia at gcc dot gnu dot org [this message] 2008-08-11 1:43 ` [Bug bootstrap/36545] " andry at inbox dot ru 2009-03-29 4:31 ` rob1weld at aol dot com 2009-03-29 4:38 ` rob1weld at aol dot com [not found] <bug-36545-4@http.gcc.gnu.org/bugzilla/> 2012-01-13 22:18 ` pinskia at gcc dot gnu.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=20080811010726.8633.qmail@sourceware.org \ --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).