public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lucier at math dot purdue dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/18211] New: Parallel bootstrap failure: No rule to make target `hard-reg-set.h', needed by `build/insn-conditions.o' Date: Thu, 28 Oct 2004 21:15:00 -0000 [thread overview] Message-ID: <20041028211517.18211.lucier@math.purdue.edu> (raw) The error message is in the subject, I guess. The build command was /bin/rm -rf *; ../configure --prefix=/export/users/lucier/local/gcc-mainline; make -j 8 bootstrap >& build.log && (make -j 12 -k check RUNTESTFLAGS="--target_board 'unix{-m64,}'">& check.log ; make mail-report-with-warnings.log; ./mail-report-with-warnings.log) -- Summary: Parallel bootstrap failure: No rule to make target `hard-reg-set.h', needed by `build/insn-conditions.o' Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: lucier at math dot purdue dot edu CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: sparc-sun-solaris2.9 GCC host triplet: sparc-sun-solaris2.9 GCC target triplet: sparc-sun-solaris2.9 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18211
next reply other threads:[~2004-10-28 21:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-28 21:15 lucier at math dot purdue dot edu [this message] 2004-10-28 21:18 ` [Bug bootstrap/18211] [4.0 Regression] " pinskia at gcc dot gnu dot org 2004-10-28 21:23 ` lucier at math dot purdue dot edu 2004-10-28 23:05 ` pinskia at gcc dot gnu dot org 2004-11-05 14:56 ` pinskia at gcc dot gnu dot org 2004-11-05 18:06 ` lucier at math dot purdue dot edu 2004-11-05 18:07 ` 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=20041028211517.18211.lucier@math.purdue.edu \ --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).