From: Jonathan Yong <10walls@gmail.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: use lt_host_flags for libstdc++.la
Date: Tue, 20 Oct 2020 02:03:15 +0000 [thread overview]
Message-ID: <11e65fda-8116-39b9-6619-fe428a7b77b6@gmail.com> (raw)
In-Reply-To: <38552260-93d1-f6a8-8eba-cb050e95b918@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 292 bytes --]
On 9/16/20 1:16 PM, JonY wrote:
> For platforms like Mingw and Cygwin, cygwin refuses to generate the
> shared library without using -no-undefined.
>
> Attached patch makes sure the right flags are used, since libtool is
> already used to link libstdc++.
>
> Patch OK?
>
Ping.
[-- Attachment #1.1.2: OpenPGP_0x713B5FE29C145D45_and_old_rev.asc --]
[-- Type: application/pgp-keys, Size: 8035 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2020-10-20 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 13:16 JonY
2020-10-20 2:03 ` Jonathan Yong [this message]
2020-11-03 0:36 ` Jonathan Yong
2020-11-03 8:24 ` Jonathan Wakely
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=11e65fda-8116-39b9-6619-fe428a7b77b6@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).