From: Greg Troxel <gdt@ir.bbn.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: "guile-config link" reports LDFLAGS it has been compiled with
Date: Mon, 18 Feb 2008 09:19:09 -0500 [thread overview]
Message-ID: <rmibq6e2vqa.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87pruwh4hn.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 17 Feb 2008 00:21:40 +0100")
Wait, no: the argument for `$CPPFLAGS' also applies to `$LDFLAGS'. That
is, if `-L' flags are passed through `$LDFLAGS' to `configure', like
`-L/path/to/gmp', then they must be reported by "guile-config link".
Admittedly, it has the undesirable side-effect of reporting completely
unrelated link flags as well. Unfortunately, I'm not sure we could
reliably filter `$LDFLAGS'.
And, this really should use -Wl,-R as well on platforms that use the -R
convention.
Strictly speaking, I think we need both LDFLAGS and -L$(libdir); it may
be that guile was built with prereqs from one place and installed in
another. But it may always put it's own libdir in LDFLAGS.
It would be nice to see a pkg-config file for guile; I kind of remember
this floating around on the list but 1.8.3 doesn't seem to install it.
next prev parent reply other threads:[~2008-02-18 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 14:57 "guile-config link" reports LDFLAGS it has been compiled with Marijn Schouten (hkBst)
2008-02-16 23:01 ` Ludovic Courtès
2008-02-16 23:21 ` Ludovic Courtès
2008-02-18 14:19 ` Greg Troxel [this message]
2008-02-18 14:59 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2008-02-18 16:45 dsmich
2008-02-18 16:53 ` 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=rmibq6e2vqa.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).