public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oyvind dot harboe at zylin dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/12548] [3.4 Regression] gcj now failes to compile included example
Date: Mon, 13 Oct 2003 09:59:00 -0000 [thread overview]
Message-ID: <20031013095903.2824.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031009101000.12548.oyvind.harboe@zylin.com>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12548
------- Additional Comments From oyvind dot harboe at zylin dot com 2003-10-13 09:59 -------
Compiling GCC isn't my forte.
I tried to compile GCC 3.4 from CVS, but it failed today:
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:74: warning: no previous
prototype for `__gthr_win32_once'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:105: warning: no previous
prototype for `__gthr_win32_key_create'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:124: warning: no previous
prototype for `__gthr_win32_key_delete'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:130: warning: no previous
prototype for `__gthr_win32_getspecific'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:141: warning: no previous
prototype for `__gthr_win32_setspecific'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:147: warning: no previous
prototype for `__gthr_win32_mutex_init_function'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:154: warning: no previous
prototype for `__gthr_win32_mutex_lock'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:163: warning: no previous
prototype for `__gthr_win32_mutex_trylock'
/home/oyvind/gcc/gcc/gcc/config/i386/gthr-win32.c:172: warning: no previous
prototype for `__gthr_win32_mutex_unlock'
m
next prev parent reply other threads:[~2003-10-13 9:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 10:10 [Bug java/12548] New: Regression, " oyvind dot harboe at zylin dot com
2003-10-09 10:10 ` [Bug java/12548] " oyvind dot harboe at zylin dot com
2003-10-09 15:12 ` [Bug java/12548] [3.4 Regression] " pinskia at gcc dot gnu dot org
2003-10-10 0:24 ` bryce at mckinlay dot net dot nz
2003-10-10 0:43 ` pinskia at gcc dot gnu dot org
2003-10-11 17:59 ` pinskia at gcc dot gnu dot org
2003-10-13 9:59 ` oyvind dot harboe at zylin dot com [this message]
2003-10-31 15:35 ` pinskia at gcc dot gnu dot org
2003-10-31 17:25 ` oyvind dot harboe at zylin dot com
2003-11-11 15:01 ` aph at gcc dot gnu dot org
2003-11-11 16:03 ` [Bug java/12548] [3.4 Regression] [non-weak] " pinskia at gcc dot gnu dot org
2003-11-11 16:04 ` [Bug middle-end/12548] " pinskia at gcc dot gnu dot org
2003-11-11 17:48 ` oyvind dot harboe at zylin dot com
2003-11-12 12:51 ` oyvind dot harboe at zylin dot com
2003-11-16 1:23 ` bryce at mckinlay dot net dot nz
2003-11-19 14:22 ` oyvind dot harboe at zylin dot com
2003-11-19 14:24 ` oyvind dot harboe at zylin dot com
2003-11-19 21:30 ` ovid at mailandnews dot com
2003-11-26 1:34 ` cvs-commit at gcc dot gnu dot org
2003-11-26 1:56 ` pinskia 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=20031013095903.2824.qmail@sources.redhat.com \
--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).