public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: tromey@redhat.com
Cc: Anthony Green <green@redhat.com>, Adam Megacz <adam@megacz.com>,
	java@gcc.gnu.org
Subject: Re: gnu/gcj/io/shs.cc doesn't compile on Solaris 2.5.1 (bootstrap 	failure)
Date: Fri, 15 Mar 2002 13:33:00 -0000	[thread overview]
Message-ID: <15506.26755.691929.593580@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87adt9y0jd.fsf@creche.redhat.com>

Tom Tromey writes:

> Could you try this patch?

close :-)  After fixing the #else/#endif nesting, the initial version
failed on Solaris 2.5.1:

/vol/gnu/src/gcc/gcc-3.1-branch-dist/libjava/gnu/gcj/io/shs.h:24: conflicting 
   types for `typedef unsigned int uint32_t'
/vol/gcc/obj/gcc-3.1-20020313/2.5.1-gcc/gcc/include/pthread.h:40: previous 
   declaration as `typedef long unsigned int uint32_t'

Taking the whole section from java/lang/mprec.h works on both
sparc-sun-solaris2.5.1 (where the bootstrap completes now; I'll run the
testsuite and post results soon) and alpha-dec-osf4.0f (where shs.c
compiles, but I get the same ICE compiling java/lang/Character.java,
details follow).

	Rainer


Index: gnu/gcj/io/shs.h
===================================================================
RCS file: /cvs/gcc/gcc/libjava/gnu/gcj/io/shs.h,v
retrieving revision 1.2
diff -u -p -r1.2 shs.h
--- shs.h	2002/02/07 05:01:29	1.2
+++ shs.h	2002/03/15 21:28:02
@@ -20,6 +20,14 @@
 #else
 # if HAVE_STDINT_H
 #  include <stdint.h>
+# else
+typedef unsigned int uint8_t __attribute__((mode(QI)));
+/* This is a blatant hack: on Solaris 2.5, pthread.h defines uint32_t
+   in pthread.h, which we sometimes include.  We protect our
+   definition the same way Solaris 2.5 does, to avoid redefining it.  */
+#  ifndef _UINT32_T
+typedef unsigned int uint32_t __attribute__((mode(SI)));
+#  endif
 # endif
 #endif
 

  reply	other threads:[~2002-03-15 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200203132014.VAA27030@tamarinde.TechFak.Uni-Bielefeld.DE>
     [not found] ` <86henk3xp5.fsf@megacz.com>
2002-03-13 14:40   ` Rainer Orth
2002-03-13 15:18     ` Adam Megacz
2002-03-13 15:40       ` Anthony Green
2002-03-14  2:56         ` Rainer Orth
2002-03-15 13:07           ` Tom Tromey
2002-03-15 13:33             ` Rainer Orth [this message]
2002-03-15 13:41               ` Tom Tromey
2002-03-15 14:45                 ` Rainer Orth
2002-04-02 18:49                   ` Tom Tromey
2002-03-15 13:43               ` Tom Tromey
2002-03-15 13:49                 ` Rainer Orth
2002-03-15 14:01                   ` Tom Tromey

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=15506.26755.691929.593580@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=adam@megacz.com \
    --cc=green@redhat.com \
    --cc=java@gcc.gnu.org \
    --cc=tromey@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).