public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/1864] bad struct statvfs declaration on Alpha when _FILE_OFFSET_BITS is defined
Date: Wed, 15 Feb 2012 18:17:00 -0000	[thread overview]
Message-ID: <bug-1864-131-Cjl7KYsgm5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-1864-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=1864

Richard Henderson <rth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |rth at gcc dot gnu.org
         Resolution|                            |FIXED

--- Comment #6 from Richard Henderson <rth at gcc dot gnu.org> 2012-02-15 18:16:37 UTC ---
This has been fixed since

commit 7ffd2bd725c3e4d77e6bfe36b76500d20427929d
Author: Richard Henderson <rth@twiddle.net>
Date:   Wed May 5 08:12:11 2010 -0700

    alpha: Do the 32/64-bit split on statfs routines.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-02-15 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-1864-131@http.sourceware.org/bugzilla/>
2012-02-15 17:46 ` jsm28 at gcc dot gnu.org
2012-02-15 18:17 ` rth at gcc dot gnu.org [this message]
2005-11-14 20:38 [Bug libc/1864] New: " tsv at solvo dot ru
2008-11-26 23:28 ` [Bug ports/1864] " drepper 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-1864-131-Cjl7KYsgm5@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).