On Thu, Feb 09, 2006 at 10:26:49AM +0100, Ralf Stephan wrote:
Regarding ngettext, I'm at a loss: configure checks for it but does not define a macro for our case. According to
http://www.delorie.com/gnu/docs/gettext/gettext_190.html
the AM_GNU_GETTEXT macro with the needs-ngettext option should take care of it all. We have that in m4/gettext.m4 but defining it in configure.ac will not find it, and I don't even know if it could break our configure. I don't see an intl/ directory, either.
The solution to this is in bug issue #1244836: either you, again, upgrade glibc, or someone with a new glibc generates a source tarball for ou,
I'm working on upgrading glibc; since I'm moving from 2.2.4 instead of something older, maybe it won't be too dangerous. I try to be careful with things that might need a rescue floppy to recover from... :) So, it might be a while before I actually install the new lib.
I don't understand how generating a source tarball on a machine with a new glibc would solve a problem for a machine with an old glibc, but that just shows how much I have to learn about autoconf/automake and the library headers.
or you only use the official source packages after we fixed that bug by upgrading the machine that creates the official inkscape sources.
I don't get any hits on that bug number via google, but I'm confused: do you mean the bug is already "fixed" (by upgrading the machine...) or will hopefully be fixed someday when the official machine is upgraded? The latter interpretation makes more sense to me, but I want to be sure I'm understanding you correctly.
Whose machine is this, anyway?
Um, it's mine, and my wife's :). She's the eventual Inkscape user, (she's an artist) with me as tech support. At the moment, it's the only machine in the house, so I don't have the luxury of experimental installations without extreme care.
Is that what you meant by "Whose machine?"
Thanks for the info,
Jim