unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Giuseppe Scrivano <gscrivano@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: missing gnulib modules
Date: Wed, 02 Sep 2009 14:25:40 +0200	[thread overview]
Message-ID: <87bplt1qkb.fsf@mandingo.thematica.it> (raw)
In-Reply-To: <87r5upy37l.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 02 Sep 2009 13:51:26 +0200")

ludo@gnu.org (Ludovic Courtès) writes:

> Hi Giuseppe,
>
> Giuseppe Scrivano <gscrivano@gnu.org> writes:
>
>> this is the error I get inside libguile/ on a pristine `master':
>>
>> gen-scmconfig.c:128:21: error: uniconv.h: No such file or directory
>
> <uniconv.h> comes from GNU libunistring.  So it looks like we got the
> CPPFLAGS wrong or something.
>
> Now, I remember that `configure' won't bail out if libunistring is not
> found (but it really should!).  Can you grep for "libunistring" in
> `config.log'?

This is what I get:

ac_cv_libunistring='no, consider installing GNU libunistring'


Now I remember that I don't have this same problem on another machine
where libunistring is installed.  I don't know if there are differences
between libunistring and the gnulib modules, in case they are the same
wouldn't be better to use the latter, considering that guile is already
using gnulib?

Cheers,
Giuseppe




  reply	other threads:[~2009-09-02 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-01  9:49 missing gnulib modules Giuseppe Scrivano
2009-09-02  8:45 ` Ludovic Courtès
2009-09-02  9:49   ` Giuseppe Scrivano
2009-09-02 11:51     ` Ludovic Courtès
2009-09-02 12:25       ` Giuseppe Scrivano [this message]
2009-09-02 13:11         ` Ludovic Courtès
2009-09-03  7:56           ` Andy Wingo
2009-09-03 15:24             ` Giuseppe Scrivano
2009-09-04 17:46             ` 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=87bplt1qkb.fsf@mandingo.thematica.it \
    --to=gscrivano@gnu.org \
    --cc=bug-guile@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).