public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/15235] New: [tree-ssa] libgfortran doesn't build on Solaris 10/x86
Date: Fri, 30 Apr 2004 20:14:00 -0000 [thread overview]
Message-ID: <20040430200445.15235.ro@techfak.uni-bielefeld.de> (raw)
Bootstrapping current tree-ssa branch with gmp 4.1.3 on i386-pc-solaris2.10
fails compiling libgfortran/runtime/environ.c:
In file included from /vol/gnu/src/gcc/gcc-tree-ssa-dist/libgfortran/runtime/environ.c:26:
/vol/gnu/src/gcc/gcc-tree-ssa-dist/libgfortran/libgfortran.h:53: error: conflicting types for 'offset_t'
/vol/gcc/obj/gcc-3.5-tree-ssa-20040429/10-gcc/gcc/include/sys/types.h:233: error: previous declaration of 'offset_t' was here
This error is similar to one reported as PR libfortran/15234 on Tru64 UNIX.
Obviously it is a recipe for disaster to use *_t type names on POSIX.1/Unix
systems ;-(
Environment:
System: SunOS erebus 5.10 s10_54 i86pc i386 i86pc
Architecture: i86pc
host: i386-pc-solaris2.10
build: i386-pc-solaris2.10
target: i386-pc-solaris2.10
configured with: /vol/gnu/src/gcc/gcc-tree-ssa-dist/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls --with-as=/vol/gcc/lib/as-7.0 --disable-libmudflap --with-gmp-dir=/vol/gnu/obj/gmp-4.1.3
How-To-Repeat:
Bootstrap the tree-ssa branch on Solaris 10 as described above.
--
Summary: [tree-ssa] libgfortran doesn't build on Solaris 10/x86
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ro at techfak dot uni-bielefeld dot de
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i386-pc-solaris2.10
GCC host triplet: i386-pc-solaris2.10
GCC target triplet: i386-pc-solaris2.10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15235
next reply other threads:[~2004-04-30 20:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 20:14 gcc-bugzilla at gcc dot gnu dot org [this message]
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
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=20040430200445.15235.ro@techfak.uni-bielefeld.de \
--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).