[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guile-1.8.1 tarball missing config.rpath

From: Ralf Wildenhues
Subject: Re: guile-1.8.1 tarball missing config.rpath
Date: Sun, 19 Nov 2006 08:16:46 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

Hello Neil,

* Neil Jerram wrote on Fri, Nov 17, 2006 at 03:19:43PM CET:
> Ralf Wildenhues <address@hidden> writes:
> > The tarball at ftp://ftp.gnu.org/gnu/guile/guile-1.8.1.tar.gz
> > has a configure script that uses the script config.rpath.  But
> > this script is not shipped with the tarball.  This can cause
> > "interesting" and weird bugs, if I remember correctly, on some
> > systems at least.  It shows up as a warning during configure.
> >
> > A likely cause for the omission is that gettextize is needed to
> > install this for you.  Also I think when you update the package
> > to use Automake 1.10, a gettext-induced check for the presence
> > of the config.rpath file will be enabled (so this doesn't happen
> > again).
> Forgive my slowness (both in responding and in understanding), but I'm
> not sure I'm clear about what possible fixes you're suggesting.  The
> two possibilities that I deduce from the above are:
> 1. Add config.rpath to Guile CVS and EXTRA_DIST in the top level
>    Makefile, so that it's always, unconditionally present.

This would be a fine choice.

> 2. Make sure that whoever prepares the release has Automake 1.10; then
>    automake --add-missing will install config.rpath as a side effect
>    of the AM_GNU_GETTEXT declaration in configure.in.

Not quite right.  automake will complain, but it will take gettextize or
autopoint to actually install config.rpath.  You could also just copy it
from /usr/share/gettext (or whereever gettext happens to be installed on
your system).  Thanks for reporting this though, the error message given
by automake is not quite right.  I'll propose a fix.

> Is that right?  Are there any other possibilities?

3. After you've once run gettextize on your package (which puts the
   config.rpath file in your package, no?), and then automake afterwards
   (the same version as you're using all the time, doesn't need to be
   1.10), the config.rpath file should be picked up automatically by the
   next 'make dist'.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]