public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/50888] Bootstrap failure in libjava against latest git glibc Date: Thu, 24 Nov 2011 08:26:00 -0000 [thread overview] Message-ID: <bug-50888-4-vfaLA0kLU5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50888-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50888 --- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-11-24 07:21:50 UTC --- Author: jakub Date: Thu Nov 24 07:21:39 2011 New Revision: 181686 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=181686 Log: PR bootstrap/50888 * prims.cc: Don't include ctype.h. (c_isspace): Define. (next_property_key, next_property_value): Use it instead of isspace. Modified: branches/gcc-4_6-branch/libjava/ChangeLog branches/gcc-4_6-branch/libjava/prims.cc
next prev parent reply other threads:[~2011-11-24 7:23 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-27 18:40 [Bug bootstrap/50888] New: " jakub at gcc dot gnu.org 2011-10-27 18:42 ` [Bug bootstrap/50888] " jakub at gcc dot gnu.org 2011-10-27 18:54 ` mark at gcc dot gnu.org 2011-10-27 23:15 ` mark at gcc dot gnu.org 2011-10-31 5:30 ` christian.joensson at gmail dot com 2011-11-16 21:18 ` pinskia at gcc dot gnu.org 2011-11-21 19:22 ` aph at gcc dot gnu.org 2011-11-22 15:37 ` jakub at gcc dot gnu.org 2011-11-22 18:34 ` aph at gcc dot gnu.org 2011-11-23 13:35 ` jakub at gcc dot gnu.org 2011-11-24 7:27 ` jakub at gcc dot gnu.org 2011-11-24 8:26 ` jakub at gcc dot gnu.org [this message] 2011-11-24 8:42 ` jakub at gcc dot gnu.org 2011-11-24 9:22 ` jakub at gcc dot gnu.org 2011-11-24 9:24 ` jakub at gcc dot gnu.org 2012-07-11 6:03 ` xguo at gcc dot gnu.org 2014-04-15 23:01 ` wade.colson at aol dot com
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-50888-4-vfaLA0kLU5@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: linkBe 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).