public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/67102] Parallel build fails in libffi/configure Date: Thu, 16 Sep 2021 17:54:21 +0000 [thread overview] Message-ID: <bug-67102-4-VZXzDmmgUJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67102-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67102 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>: https://gcc.gnu.org/g:db1a65d9364fe72c2fff65fb2dec051728b6f3fa commit r12-3583-gdb1a65d9364fe72c2fff65fb2dec051728b6f3fa Author: Andrew Pinski <apinski@marvell.com> Date: Wed Sep 15 09:51:08 2021 +0000 Fix PR 67102: Add libstdc++ dependancy to libffi The error message is obvious -funconfigured-libstdc++-v3 is used on the g++ command line. So we just add the dependancy. OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions. ChangeLog: PR bootstrap/67102 * Makefile.def: Have configure-target-libffi depend on all-target-libstdc++-v3. * Makefile.in: Regenerate.
next prev parent reply other threads:[~2021-09-16 17:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-03 15:30 [Bug libffi/67102] New: " dilyan.palauzov at aegee dot org 2021-09-15 9:47 ` [Bug bootstrap/67102] " pinskia at gcc dot gnu.org 2021-09-15 10:03 ` pinskia at gcc dot gnu.org 2021-09-15 20:57 ` pinskia at gcc dot gnu.org 2021-09-16 17:54 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-16 17:55 ` pinskia at gcc dot gnu.org 2022-01-25 17:47 ` cvs-commit 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-67102-4-VZXzDmmgUJ@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).