public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/32857] libjava fails to build on hppa-linux-gnu (ICE in simplify_subreg) Date: Sun, 22 Jul 2007 21:03:00 -0000 [thread overview] Message-ID: <20070722210256.24279.qmail@sourceware.org> (raw) In-Reply-To: <bug-32857-5724@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from danglin at gcc dot gnu dot org 2007-07-22 21:02 ------- Do you have Kyle's use-compat_sys_getdents patch installed? It fixes a scandir bug. Without it, building libjava fails. See <http://git.kernel.org/?p=linux/kernel/git/kyle/patches.git;a=shortlog>. It was also posted to parisc list. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32857
next prev parent reply other threads:[~2007-07-22 21:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-22 20:14 [Bug java/32857] New: " debian-gcc at lists dot debian dot org 2007-07-22 20:16 ` [Bug target/32857] " pinskia at gcc dot gnu dot org 2007-07-22 21:03 ` danglin at gcc dot gnu dot org [this message] 2008-01-27 0:15 ` danglin at gcc dot gnu dot org 2008-01-27 0:25 ` debian-gcc at lists dot debian dot org 2008-01-27 4:18 ` debian-gcc at lists dot debian dot org 2008-01-27 7:10 ` dave at hiauly1 dot hia dot nrc dot ca
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=20070722210256.24279.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: 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).