From: Manfred Hollstein <manfred@s-direktnet.de>
To: mmitchell@usa.net, law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: Texino build problem
Date: Sun, 29 Mar 1998 05:14:00 -0000 [thread overview]
Message-ID: <13597.4904.293678.292507@saturn.s-direktnet.de> (raw)
In-Reply-To: <199803270116.RAA04845@mail.earthlink.net>
On Thu, 26 March 1998, 17:16:47, mmitchell@usa.net wrote:
On mips-sgi-irix6.4 I now get:
make[3]: Entering directory `/pooma/mitchell/egcs/objdir/texinfo/lib'
make[3]: *** No rule to make target `-c', needed by `all'. Stop.
Indeed, it looks like:
all: Makefile $(LIBRARIES) $(DATA)
DATA = $(INSTALL_DATA)
INSTALL_DATA = ${INSTALL} -m 644
INSTALL = ../../../texinfo/../install-sh -c
Does anyone comprehend this situation?
Yep, I do. Makefile.in is now a generated file which depends on
Makefile.in -> { Makefile.am, configure.in, aclocal.m4}
We now have to remember, that we need to rebuild the various
Makefile.in files after changing configure.in (this unfortunately
needs automake-1.2f, which I don't know where to get from. Jeff, do
you know?). You obviously are having automake-1.2e installed (as I do,
too), which generates these broken Makefile.in's.
The current sources in CVS look consistent with only timestamp
problems. The following command should do the trick (it did it for me):
$ cd egcs/texinfo
$ touch `find . -name Makefile.in -print`
If configure is out of date, you need to execute the following
commands in between the two:
$ mv configure configure.orig
$ autoconf
$ touch --file=configure.orig configure
$ autoheader
$ touch --file=configure config.h.in
manfred
next prev parent reply other threads:[~1998-03-29 5:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-26 17:15 Mark Mitchell
1998-03-29 5:14 ` H.J. Lu
1998-03-29 5:14 ` Manfred Hollstein [this message]
1998-04-02 11:32 ` Raja R Harinath
1998-04-02 3:41 ` Richard Henderson
[not found] ` <d91zvi3dp2.fsf.cygnus.egcs@sejong.cs.umn.edu>
1998-04-04 14:20 ` Tom Tromey
1998-04-04 20:05 ` Jeffrey A Law
1998-04-06 18:30 ` Jim Wilson
1998-04-07 19:34 ` Jeffrey A Law
1998-04-07 19:34 ` Tom Tromey
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13597.4904.293678.292507@saturn.s-direktnet.de \
--to=manfred@s-direktnet.de \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=mmitchell@usa.net \
/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).