From: Richard Coleman <coleman@math.gatech.edu>
To: zsh-workers@math.gatech.edu
Subject: Re: beta11-test9 available for testing
Date: Wed, 11 Oct 1995 12:56:13 -0400 [thread overview]
Message-ID: <9510111656.AA21968@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Wed, 11 Oct 1995 09:32:16 BST." <199510110832.JAA10313@bolyai.cs.elte.hu>
> > Shit, I forgot which files i have to touch, will have to find out again...
>
> Sorry about that. I never do a make in the top directory, that's why I always
> forget it. Also I do not have autoconf (I was too lazy to get it). For those
> having such problems, just do a `touch configure' in the main zsh directory.
> I repacked the tar.gz source with correct dates. The only change is the date
> of configure, so do not download it if you already have it. The file changed
> is:
>
> -rw-r--r-- 616509 Oct 11 09:01 zsh-2.6-beta11-test9-hzoli11.tar.gz
>
> If you use the patch to vanilla test9, you will probably have similar
> problems, but I do not repack the patch file.
There are two things I could do. The first is put in a Makefile target
so that "make touch" will touch all the right files in the right order.
The second is add some code to the "make dist" code so that when I
make a distribution, it comments out the Makefile dependencies for
configure. That way if a patch changes configure or configure.in, then
it will not try to run autoconf or autoheader.
Hmm... I think I like the second option. I'll try to work on it
later this week.
Richard Coleman
coleman@math.gatech.edu
next prev parent reply other threads:[~1995-10-11 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199510110809.AA17690@zditr1.arcs.ac.at>
1995-10-11 8:32 ` Zoltan Hidvegi
1995-10-11 16:56 ` Richard Coleman [this message]
1995-10-10 0:52 Richard Coleman
1995-10-10 21:39 ` Zoltan Hidvegi
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=9510111656.AA21968@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).