From: "Ludovic Courtès" <ludo@gnu.org>
To: Cyprien Nicolas <cyprien@nicolas.tf>
Cc: 36339@debbugs.gnu.org
Subject: bug#36339: generated .pc files leaks build-time LDFLAGS
Date: Mon, 24 Jun 2019 15:17:44 +0200 [thread overview]
Message-ID: <8736jzazrb.fsf@gnu.org> (raw)
In-Reply-To: <db856c28-4467-64f3-6937-2280aa5f5c7d@nicolas.tf> (Cyprien Nicolas's message of "Sun, 23 Jun 2019 11:19:52 +0200")
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Hello,
Cyprien Nicolas <cyprien@nicolas.tf> skribis:
> These flags are private to the way I built guile, and should not
> affect packages using guile later.
>
> I have observed this behavior in guile-2.0, 2.2.5 and 2.9.2.
>
> -----8<-----8<-----8<-----8<-----8<-----
> Name: GNU Guile
> Description: GNU's Ubiquitous Intelligent Language for Extension
> Version: 2.0.14
> Libs: -L${libdir} -lguile-2.0 -lgc
> Libs.private: -lgmp -lltdl -L/usr/lib64/../lib64 -lffi \
> -lunistring -Wl,-O1 -Wl,--as-needed -lcrypt -lm \
> \
>
> Cflags: -I${pkgincludedir}/2.0 -pthread
> ----->8----->8----->8----->8----->8-----
I believe the attached patch should fix it. Could you confirm?
Thanks,
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 291 bytes --]
diff --git a/configure.ac b/configure.ac
index 9073deba0..92966ce34 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1688,7 +1688,7 @@ do
done
GUILE_CFLAGS="$GUILE_CFLAGS $PTHREAD_CFLAGS"
-GUILE_LIBS="$LDFLAGS $LIBS"
+GUILE_LIBS="$LIBS"
AC_SUBST(GUILE_LIBS)
AC_SUBST(GUILE_CFLAGS)
next prev parent reply other threads:[~2019-06-24 13:17 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 [this message]
2019-07-07 12:45 ` Cyprien Nicolas
2019-07-07 13:09 ` Ludovic Courtès
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=8736jzazrb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36339@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).