public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/53879] [4.6] new glibc: sysinfo.go:5976:68: error: expected ‘{’
Date: Fri, 13 Jul 2012 08:21:00 -0000	[thread overview]
Message-ID: <bug-53879-4-mwYUg75PU0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53879-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53879

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
            Version|4.8.0                       |4.6.4
         Resolution|FIXED                       |
            Summary|new glibc:                  |[4.6] new glibc:
                   |sysinfo.go:5976:68: error:  |sysinfo.go:5976:68: error:
                   |expected ‘{’                |expected ‘{’

--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-07-13 08:20:43 UTC ---
It still seems to affect the 4.6 branch:

sysinfo.go:3681:63: error: expected '{'
sysinfo.go:3681:63: error: expected ';' or '}' or newline
sysinfo.go:3681:80: error: expected field name


  parent reply	other threads:[~2012-07-13  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 15:46 [Bug go/53879] New: " jan.kratochvil at redhat dot com
2012-07-09 15:42 ` [Bug go/53879] " ian at airs dot com
2012-07-13  8:21 ` jan.kratochvil at redhat dot com [this message]
2012-07-13 17:47 ` [Bug go/53879] [4.6] " ian at airs dot com
2012-07-14 18:36 ` jan.kratochvil at redhat 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-53879-4-mwYUg75PU0@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: link
Be 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).