unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: "guile-config link" reports LDFLAGS it has been compiled with
Date: Sun, 17 Feb 2008 00:01:42 +0100	[thread overview]
Message-ID: <878x1kijzd.fsf@gnu.org> (raw)
In-Reply-To: 47653CEA.9090601@gentoo.org

Hi Marijn,

Sorry for the later reply.

"Marijn Schouten (hkBst)" <hkBst@gentoo.org> writes:

> "guile-config link" reports LDFLAGS it has been compiled with. Usage says:
>
>   guile-config link        - print libraries to link with
>
> so one of these is inaccurate. To resolve this issue in favor of the description:
>
> --- guile-1.8.3.orig/configure.in
> +++ guile-1.8.3/configure.in
> @@ -1333,7 +1333,7 @@ AC_SUBST(LIBGUILE_SRFI_SRFI_60_INTERFACE
>  #######################################################################
>
>  dnl Tell guile-config what flags guile users should compile and link with.
> -GUILE_LIBS="$LDFLAGS $LIBS"
> +GUILE_LIBS="$LIBS"
>  GUILE_CFLAGS="$PTHREAD_CFLAGS"
>  AC_SUBST(GUILE_LIBS)
>  AC_SUBST(GUILE_CFLAGS)
>
> as reported in http://bugs.gentoo.org/show_bug.cgi?id=202205

Indeed, you're right.

Conversely, I think `GUILE_CFLAGS' must include `$CPPFLAGS' since this
may include `-I' flags that are required (e.g., `-I/path/to/gmp').

Thanks,
Ludovic.





  reply	other threads:[~2008-02-16 23:01 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 [this message]
2008-02-16 23:21   ` Ludovic Courtès
2008-02-18 14:19     ` Greg Troxel
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=878x1kijzd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@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).