public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/15235] [gfortran] libgfortran doesn't build on Solaris 10/x86
Date: Sat, 15 May 2004 00:46:00 -0000 [thread overview]
Message-ID: <20040514171740.2671.qmail@sourceware.org> (raw)
In-Reply-To: <20040430200445.15235.ro@techfak.uni-bielefeld.de>
------- Additional Comments From ro at techfak dot uni-bielefeld dot de 2004-05-14 17:17 -------
Subject: Re: [gfortran] libgfortran doesn't build on Solaris 10/x86
Tobias dot Schlueter at physik dot uni-muenchen dot de writes:
> Yeah, seems like this is the right thing to do. I will prepare a patch
> to this effect later today. I.e. use off_t in all places.
Fine, thanks.
> Besides, I'm curious, is offset_t different from off_t on Solaris?
Yes, off_t can be 32 bit or 64 bit: always 64 bit for 64-bit compilations,
either one for 32-bit compilations, depending on large file support, while
offset_t is always 64 bit:
/*
* The size of off_t and related types depends on the setting of
* _FILE_OFFSET_BITS. (Note that other system headers define other types
* related to those defined here.)
[...]
#if defined(_LP64) || _FILE_OFFSET_BITS == 32
typedef long off_t; /* offsets within files */
#elif _FILE_OFFSET_BITS == 64
typedef longlong_t off_t; /* offsets within files */
#endif
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15235
next prev parent reply other threads:[~2004-05-14 17:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 20:14 [Bug fortran/15235] New: [tree-ssa] " gcc-bugzilla at gcc dot gnu dot org
2004-04-30 20:20 ` [Bug libfortran/15235] " pinskia at gcc dot gnu dot org
2004-05-14 21:14 ` [Bug libfortran/15235] [gfortran] " tobi at gcc dot gnu dot org
2004-05-14 21:20 ` ro at techfak dot uni-bielefeld dot de
2004-05-15 0:42 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-15 0:46 ` ro at techfak dot uni-bielefeld dot de [this message]
2004-05-15 3:40 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-15 3:49 ` ro at techfak dot uni-bielefeld dot de
2004-05-15 9:03 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2004-05-15 9:46 ` tobi at gcc dot gnu dot org
2004-05-16 18:59 ` pinskia at gcc dot gnu dot org
2004-05-18 0:48 ` [Bug libfortran/15235] [gfortran] libgfortran doesn't build on Solaris ro at techfak dot uni-bielefeld dot de
2004-05-19 5:14 ` cvs-commit at gcc dot gnu dot org
2004-05-19 9:30 ` tobi at gcc dot gnu dot org
2004-05-19 9:56 ` ro at techfak dot uni-bielefeld dot de
2004-08-11 21:56 ` [Bug libfortran/15235] " pinskia at gcc dot gnu dot org
2004-09-20 16:12 ` tobi at gcc dot gnu dot org
2004-09-27 14:29 ` tobi at gcc dot gnu dot org
2004-12-27 14:46 ` pinskia at gcc dot gnu dot org
2005-01-01 12:14 ` ebotcazou at gcc dot gnu dot org
2005-01-06 14:40 ` tobi at gcc dot gnu dot org
2005-04-16 22:33 ` pinskia at gcc dot gnu dot org
2005-05-31 16:45 ` [Bug libfortran/15235] libgfortran doesn't build on Solaris 10 ebotcazou at gcc dot gnu dot 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=20040514171740.2671.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: 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).