unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: bug-guile@gnu.org, bug-autoconf@gnu.org,
	Sergei Steshenko <sergstesh@yahoo.com>
Subject: Re: guile-1.8.1 tarball missing config.rpath
Date: Sun, 19 Nov 2006 08:16:46 +0100	[thread overview]
Message-ID: <20061119071645.GC28934@iam.uni-bonn.de> (raw)
In-Reply-To: <87y7qaqhog.fsf@ossau.uklinux.net>

Hello Neil,

* Neil Jerram wrote on Fri, Nov 17, 2006 at 03:19:43PM CET:
> Ralf Wildenhues <Ralf.Wildenhues@gmx.de> 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'.

Cheers,
Ralf




  reply	other threads:[~2006-11-19  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061107101431.GD21880@iam.uni-bonn.de>
     [not found] ` <20061107110254.36074.qmail@web35215.mail.mud.yahoo.com>
2006-11-07 18:54   ` guile-1.8.1 tarball missing config.rpath (was: 'make check' for autogen-5.8.7 fails - possibly an autoconf bug) Ralf Wildenhues
2006-11-17 14:19     ` guile-1.8.1 tarball missing config.rpath Neil Jerram
2006-11-19  7:16       ` Ralf Wildenhues [this message]
2006-12-02 22:52         ` Kevin Ryde

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=20061119071645.GC28934@iam.uni-bonn.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=bug-autoconf@gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=sergstesh@yahoo.com \
    /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).