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 11:49:10 +0200 [thread overview]
Message-ID: <87fxb51xt5.fsf@mandingo.thematica.it> (raw)
In-Reply-To: <87ab1d20qz.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 02 Sep 2009 10:45:40 +0200")
Hello,
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
gen-scmconfig.c: In function ‘main’:
gen-scmconfig.c:430: error: ‘iconveh_error’ undeclared (first use in this function)
gen-scmconfig.c:430: error: (Each undeclared identifier is reported only once
gen-scmconfig.c:430: error: for each function it appears in.)
gen-scmconfig.c:432: error: ‘iconveh_question_mark’ undeclared (first use in this function)
gen-scmconfig.c:434: error: ‘iconveh_escape_sequence’ undeclared (first use in this function)
make[2]: *** [gen-scmconfig.o] Error 1
Cheers,
Giuseppe
ludo@gnu.org (Ludovic Courtès) writes:
> Hi!
>
> Giuseppe Scrivano <gscrivano@gnu.org> writes:
>
>> I got some linker errors while compiling the latest guile git revision.
>
> In `master', right?
>
> I don't have any problems, but it could be that I have stale Gnulib
> files anyway.
>
> Can you post the exact error messages? (You need to start from a
> pristine tree where you haven't run `gnulib-tool'.)
>
> Thanks,
> Ludo'.
next prev parent reply other threads:[~2009-09-02 9:49 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 [this message]
2009-09-02 11:51 ` Ludovic Courtès
2009-09-02 12:25 ` Giuseppe Scrivano
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=87fxb51xt5.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).