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 d/102574] d: gdc driver ignores -static-libstdc++ when automatically linking libstdc++ library
Date: Mon, 04 Oct 2021 15:59:37 +0000 [thread overview]
Message-ID: <bug-102574-4-doxzDL4smA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102574-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102574
--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>:
https://gcc.gnu.org/g:c86a16b07b76604a8e3d556f135babab80e2b747
commit r12-4146-gc86a16b07b76604a8e3d556f135babab80e2b747
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date: Sun Oct 3 16:02:24 2021 +0200
d: gdc driver ignores -static-libstdc++ when automatically linking
libstdc++ library
Adds handling of `-static-libstc++' in the gdc driver, so that libstdc++
is appropriately linked if libstdc++ is either needed or seen on the
command-line.
PR d/102574
gcc/d/ChangeLog:
* d-spec.cc (lang_specific_driver): Link libstdc++ statically if
-static-libstdc++ was given on command-line.
next prev parent reply other threads:[~2021-10-04 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 13:37 [Bug d/102574] New: " ibuclaw at gdcproject dot org
2021-10-04 15:59 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-04 17:08 ` [Bug d/102574] " cvs-commit at gcc dot gnu.org
2021-10-04 17:08 ` cvs-commit at gcc dot gnu.org
2021-10-04 17:08 ` cvs-commit at gcc dot gnu.org
2021-10-04 17:10 ` ibuclaw at gdcproject 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=bug-102574-4-doxzDL4smA@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: link
Be 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).