From: "Ludovic Courtès" <ludo@gnu.org>
To: Cyprien Nicolas <cyprien@nicolas.tf>
Cc: 36339-done@debbugs.gnu.org
Subject: bug#36339: generated .pc files leaks build-time LDFLAGS
Date: Sun, 07 Jul 2019 15:09:29 +0200 [thread overview]
Message-ID: <875zoedm9i.fsf@gnu.org> (raw)
In-Reply-To: <36ab6c81-15a2-440f-4329-4d7bf9652141@nicolas.tf> (Cyprien Nicolas's message of "Sun, 7 Jul 2019 14:45:14 +0200")
Hi Cyprien,
Cyprien Nicolas <cyprien@nicolas.tf> skribis:
> On 24/06/2019 15:17, Ludovic Courtès wrote:
>>
>> I believe the attached patch should fix it. Could you confirm?
>
> Yes it does, tested on 2.2.6 and 2.9.2. All arch-dependent binaries have
> been built with the right LDFLAGS, and the pkgconfig file looks clean.
Awesome. Pushed as a69b567d97f7c9193924c775e1dd86e43a35b8bd to the
‘stable-2.2’ branch.
Thanks!
Ludo’.
prev parent reply other threads:[~2019-07-07 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 9:19 bug#36339: generated .pc files leaks build-time LDFLAGS Cyprien Nicolas
2019-06-24 13:17 ` Ludovic Courtès
2019-07-07 12:45 ` Cyprien Nicolas
2019-07-07 13:09 ` Ludovic Courtès [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zoedm9i.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36339-done@debbugs.gnu.org \
--cc=cyprien@nicolas.tf \
/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).