public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/98504] [11 Regression] bootstrap broken in libgo on ia64-linux-gnu Date: Sun, 03 Jan 2021 12:10:16 +0000 [thread overview] Message-ID: <bug-98504-4-64fkTvHhCS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98504-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98504 --- Comment #1 from Matthias Klose <doko at debian dot org> --- make[6]: *** [Makefile:2962: runtime.lo] Error 1 make[6]: Leaving directory '/<<PKGBUILDDIR>>/build/ia64-linux-gnu/libgo' make[5]: *** [Makefile:2292: all-recursive] Error 1 make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/ia64-linux-gnu/libgo' make[4]: *** [Makefile:1187: all] Error 2 make[4]: Leaving directory '/<<PKGBUILDDIR>>/build/ia64-linux-gnu/libgo' make[3]: *** [Makefile:21385: all-target-libgo] Error 2
next prev parent reply other threads:[~2021-01-03 12:10 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-03 12:08 [Bug go/98504] New: " doko at debian dot org 2021-01-03 12:10 ` doko at debian dot org [this message] 2021-01-03 12:17 ` [Bug go/98504] " schwab@linux-m68k.org 2021-01-04 21:16 ` ian at airs dot com 2021-01-05 11:17 ` rguenth at gcc dot gnu.org 2021-02-01 15:55 ` [Bug lto/98504] " doko at debian dot org 2021-04-09 8:02 ` rguenth at gcc dot gnu.org 2021-04-09 8:34 ` glaubitz at physik dot fu-berlin.de 2021-04-27 11:40 ` [Bug lto/98504] [11/12 " jakub at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-01-17 15:05 ` rguenth at gcc dot gnu.org 2022-01-17 15:07 ` glaubitz at physik dot fu-berlin.de 2022-01-18 19:06 ` glaubitz at physik dot fu-berlin.de 2022-01-18 21:25 ` ian at airs dot com 2022-01-18 22:02 ` glaubitz at physik dot fu-berlin.de 2022-01-19 7:33 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:03 ` [Bug lto/98504] [11/12/13/14 " jakub at gcc dot gnu.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=bug-98504-4-64fkTvHhCS@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).