From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: bug-guile@gnu.org
Subject: Re: cvs guile build/install problems
Date: 17 Apr 2002 00:21:44 +0200 [thread overview]
Message-ID: <87ads35lon.fsf@zagadka.ping.de> (raw)
In-Reply-To: <0203280230570L.17464@locke.free-expression.org>
Lynn Winebarger <owinebar@free-expression.org> writes:
> On Wednesday 20 March 2002 16:51, Marius Vollmer wrote:
> > Sorry, I tested with the wrong file. But automake will also install
> > doc/tutorial/mdate-sh for me:
> >
> > $ rm doc/tutorial/mdate-sh
> > $ rm doc/ref/mdate-sh
> > $ ./autogen.sh
> > autoheader2.50: libguile/scmconfig.h.in is unchanged
> > doc/ref/Makefile.am:24: installing `doc/ref/mdate-sh'
> > doc/tutorial/Makefile.am:24: installing `doc/tutorial/mdate-sh'
>
> I haven't tracked down the specific problem, but I can say that
> invoking autogen.sh twice will install doc/tutorial/mdate-sh the
> second time (but not the first when it's right out of CVS). It
> installs doc/ref/mdate-sh the first time. I'm making a separate
> copy of the directory for building.
I can confirm this now. The snapshots fall over because of this as
well. It is a bug in automake, as far as I can see. The workaround
for now is to invoke automake twice from autogen.sh (committed). I'll
go and gently slap the automake guys for this.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-04-16 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <02030414141506.10124@locke.free-expression.org>
[not found] ` <87lmcz54pm.fsf@zagadka.ping.de>
2002-03-16 6:24 ` cvs guile build/install problems Lynn Winebarger
2002-03-20 21:51 ` Marius Vollmer
2002-03-28 7:30 ` Lynn Winebarger
2002-03-28 14:36 ` Lynn Winebarger
2002-04-01 8:23 ` Lynn Winebarger
2002-04-16 22:21 ` Marius Vollmer [this message]
2002-03-26 3:02 ` Thien-Thi Nguyen
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=87ads35lon.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=bug-guile@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).