unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: No declaration for isblank
Date: Wed, 30 Jan 2008 22:19:58 +0000	[thread overview]
Message-ID: <873asfufap.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87myqn35u8.fsf@dellish.bordeaux.inria.fr> (Ludovic Courtès's message of "Wed, 30 Jan 2008 12:34:07 +0100")

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

> Hi,
>
> I'm slowly getting back to Guile, and the first thing I came across was
> this old Gnulib-related bootstrap issue (HEAD).
>
> ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
>> My `gnulib-cache.m4' is the same as the one in CVS HEAD:
>>
>>   http://cvs.savannah.gnu.org/viewvc/guile/guile-core/m4/gnulib-cache.m4?revision=1.1&root=guile&view=markup
>>
>> It contains the line "gl_MODULES([alloca strcase])" so `gnulib-tool'
>> must at least pull the `alloca' and `strcase' modules.  It should also
>> pull their dependencies; `strcase' happens to depend on `string', which
>> in turn depends on `extensions', the module that ensures `_GNU_SOURCE'
>> is defined when available.
>>
>> (Actually, we should be importing `extensions' explicitly rather than
>> rely on this side effect.)
>
> I followed my own suggestion and added `extensions' to the list of
> required modules, since it turns out that it was no longer pulled by the
> other modules.  Hopefully, that fixes this very problem once for all.

Sounds good.  I think most of this problem was actually me not
understanding how gnulib works, but I agree that it makes sense to
import extensions explicitly.

> On a related note, when bootstrapping, `autoreconf' complains that we're
> using `AM_GNU_GETTEXT' without having `po' in `SUBDIRS'---which is
> normal since no string is internationalized.  Still, is there something
> we could do about it?

I guess we could start some token internationalization...  Perhaps we
could start with the "ERROR" in display_header(), and who knows where
that might lead?  Translation of Guile's messages can only be a good
thing, n'est-ce pas?

(On the other hand, I haven't noticed anyone clamouring for this.)

> Thanks,
> Ludovic.

Regards,
        Neil





  reply	other threads:[~2008-01-30 22:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 21:25 No declaration for isblank Neil Jerram
2007-09-19 21:31 ` No declaration for cuserid Neil Jerram
2007-09-20  7:34 ` No declaration for isblank Ludovic Courtès
2007-10-21 21:13   ` Neil Jerram
2007-10-21 21:22     ` Neil Jerram
2007-10-21 21:51       ` Ludovic Courtès
2007-10-23 14:06         ` Neil Jerram
2007-10-23 14:27           ` Ludovic Courtès
2007-10-24 10:30             ` Neil Jerram
2007-10-24 11:19               ` Ludovic Courtès
2008-01-30 11:34                 ` Ludovic Courtès
2008-01-30 22:19                   ` Neil Jerram [this message]
2008-01-31  9:21                     ` String translation Ludovic Courtès
2008-02-01 20:46                       ` Neil Jerram
2007-10-24 11:30               ` No declaration for isblank Neil Jerram

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=873asfufap.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --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).