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/106156] [13 Regression] libtool fails to link liblto_plugin.la on riscv64-linux-gnu Date: Thu, 14 Jul 2022 11:27:52 +0000 [thread overview] Message-ID: <bug-106156-4-nFWibq9Fyz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106156-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106156 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:29f40a8047fa9b6ccde2174ca126b78a535e1a61 commit r13-1696-g29f40a8047fa9b6ccde2174ca126b78a535e1a61 Author: Martin Liska <mliska@suse.cz> Date: Thu Jul 14 09:51:33 2022 +0200 lto-plugin: use -pthread only for detected targets Use -pthread only if we are going to use pthread functionality. PR bootstrap/106156 lto-plugin/ChangeLog: * Makefile.am: Use ac_lto_plugin_extra_ldflags for AM_LDFLAGS. * configure.ac: Use AC_SUBST(ac_lto_plugin_extra_ldflags). * Makefile.in: Regenerate. * configure: Regenerate.
next prev parent reply other threads:[~2022-07-14 11:27 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-01 4:26 [Bug bootstrap/106156] New: " doko at gcc dot gnu.org 2022-07-01 7:06 ` [Bug bootstrap/106156] " rguenth at gcc dot gnu.org 2022-07-01 7:28 ` marxin at gcc dot gnu.org 2022-07-04 10:24 ` marxin at gcc dot gnu.org 2022-07-04 10:31 ` pinskia at gcc dot gnu.org 2022-07-04 11:03 ` marxin at gcc dot gnu.org 2022-07-04 11:32 ` marxin at gcc dot gnu.org 2022-07-08 11:21 ` marxin at gcc dot gnu.org 2022-07-13 7:35 ` doko at gcc dot gnu.org 2022-07-13 7:40 ` marxin at gcc dot gnu.org 2022-07-14 11:27 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-14 11:28 ` marxin 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-106156-4-nFWibq9Fyz@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).