public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49052] i386 version of gcc-4.5 fails to compile C or Fortran files on CIFS mounts
Date: Thu, 19 May 2011 09:26:00 -0000	[thread overview]
Message-ID: <bug-49052-4-SWzggayzfF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49052-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|---                         |4.6.0

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-19 08:58:43 UTC ---
The issue is that gcc < 4.6 does not have large file support enabled and so
on 32bit hosts with 64bit file systems you can get this if the inode number
does not fit in the 32bit stat structure.  That's what we have seen on
32bit userland with 64bit kernels and big fs.

Should be fixed for 4.6.


  parent reply	other threads:[~2011-05-19  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 20:45 [Bug fortran/49052] New: " marconifabio@ubuntu-it.org
2011-05-18 20:55 ` [Bug fortran/49052] " marconifabio@ubuntu-it.org
2011-05-19  9:26 ` rguenth at gcc dot gnu.org [this message]
2011-05-19  9:43 ` jb 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=bug-49052-4-SWzggayzfF@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).