public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/9741] [hppa-linux] ICE (segfault) while building a cross compiler Date: Wed, 03 Sep 2003 05:54:00 -0000 [thread overview] Message-ID: <20030903055413.30024.qmail@sources.redhat.com> (raw) In-Reply-To: <20030218114601.9741.jbglaw@lug-owl.de> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9741 pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID ------- Additional Comments From pinskia at gcc dot gnu dot org 2003-09-03 05:54 ------- This is invalid as you have to use --with-headers and with the glibc/linux kernel headers on almost all *-*-linux-gnu.
prev parent reply other threads:[~2003-09-03 5:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030218114601.9741.jbglaw@lug-owl.de> 2003-06-15 9:09 ` jbglaw@lug-owl.de 2003-06-15 16:55 ` dhazeghi@yahoo.com 2003-07-18 19:52 ` dhazeghi at yahoo dot com 2003-09-03 5:54 ` pinskia at gcc dot gnu dot org [this message]
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=20030903055413.30024.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: 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).