From: "Germán Arias" <german@xelalug.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Problem to compile g-wrap
Date: Tue, 04 Oct 2011 18:00:14 -0600 [thread overview]
Message-ID: <1317772814.9047.4.camel@german-desktop> (raw)
In-Reply-To: <87y5x05yf3.fsf@gnu.org>
On mar, 2011-10-04 at 21:50 +0200, Ludovic Courtès wrote:
> Hi,
>
> Germán Arias <german@xelalug.org> skribis:
>
> > checking size of size_t... 4
> > checking size of ssize_t... 4
> > checking for guile... /usr/local/bin/guile
> > checking for guile-config... /usr/local/bin/guile-config
> > checking for guile-tools... /usr/local/bin/guile-tools
> > checking libguile compile flags... -pthread
> > -I/usr/local/include/guile/2.0 -I/usr/local/include
> > checking libguile link flags... -L/usr/local/lib -lguile-2.0 -lgc
> > checking for guile-2.0... no
> >
> >
> > Why? the Guile libraries are just there.
>
> Presumably it’s running ‘pkg-config guile-2.0’, which fails. Can you
> check whether guile-2.0.pc is in $PKG_CONFIG_PATH?
>
> HTH,
> Ludo’.
>
PKG_CONFIG_PATH is empty. So I do:
export
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/usr/share/pkgconfig
guile-2.0.pc is at /usr/local/lib/pkgconfig. But I get the same output.
Which should be the output of 'pkg-config guile-2.0'? If I run this, I
get:
german@german-desktop:~/Instalados/g-wrap-1.9.13$ pkg-config guile-2.0
german@german-desktop:~/Instalados/g-wrap-1.9.13$
Thanks.
next prev parent reply other threads:[~2011-10-05 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 23:53 Problem to compile g-wrap Germán Arias
2011-10-03 22:58 ` Germán Arias
2011-10-04 19:50 ` Ludovic Courtès
2011-10-05 0:00 ` Germán Arias [this message]
2011-10-05 10:11 ` Ludovic Courtès
2011-10-06 6:12 ` Germán Arias
2011-10-06 19:07 ` Ludovic Courtès
2011-10-07 18:31 ` Germán Arias
2011-10-12 13:26 ` Paul Emsley
2011-10-15 21:55 ` Germán Arias
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=1317772814.9047.4.camel@german-desktop \
--to=german@xelalug.org \
--cc=guile-user@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).