From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: zsh-5.0.5-dev-1
Date: Mon, 11 Aug 2014 17:39:31 +0100 [thread overview]
Message-ID: <20140811173931.74e51ca2@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20140811163001.GI6176@sym.noone.org>
On Mon, 11 Aug 2014 18:30:02 +0200
Axel Beckert <abe@deuxchevaux.org> wrote:
> It seems as if commit 3c25cb29aba4d4c1a907aa29db48c36d8dbac18e mixed
> up source and build directories and hence broke out of tree building.
Yes, crossed with my last message.
> At least the following patch fixes it for me:
It looks like there's one more that needs changing in the TEXI2HTML =
macro assignment (I'm not quite sure how it works without that).
> Haven't yet tested it with in-tree-building though. I'm also slightly
> surprised that this only came up now. That commit is from January. So
> maybe I'm still missing something else...
I think the habit of building files in a different location from the
source isn't very frequent at the moment; furthermore if one of your
builds uses that directory you probably get the file you need.
pws
next prev parent reply other threads:[~2014-08-11 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140810191241.38519e4d@pws-pc.ntlworld.com>
2014-08-11 16:06 ` zsh-5.0.5-dev-1 Axel Beckert
2014-08-11 16:08 ` zsh-5.0.5-dev-1 Axel Beckert
2014-08-11 16:27 ` zsh-5.0.5-dev-1 Peter Stephenson
2014-08-11 16:30 ` zsh-5.0.5-dev-1 Axel Beckert
2014-08-11 16:39 ` Peter Stephenson [this message]
2014-08-11 16:45 ` zsh-5.0.5-dev-1 Bart Schaefer
2014-08-11 16:46 ` zsh-5.0.5-dev-1 Axel Beckert
2014-08-11 18:42 ` zsh-5.0.5-dev-1 Axel Beckert
2014-08-12 8:43 ` zsh-5.0.5-dev-1 Peter Stephenson
2014-08-11 17:24 ` Raw ^A in Doc/Makefile.in on purpose? (was: zsh-5.0.5-dev-1) Axel Beckert
2014-08-11 17:33 ` Bart Schaefer
2014-08-11 17:37 ` Axel Beckert
2014-08-11 18:31 ` Axel Beckert
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=20140811173931.74e51ca2@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.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.
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).