Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Previous zsh.yo.in patch wasn't good enough
- X-seq: zsh-workers 8886
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Clint Adams <schizo@xxxxxxxxxx>
- Subject: Re: PATCH: Previous zsh.yo.in patch wasn't good enough
- Date: Fri, 3 Dec 1999 16:43:15 +0000
- Cc: zsh-workers@xxxxxxxxxxxxxx
- In-reply-to: <19991203105517.A27004@xxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <991203151631.ZM18044@xxxxxxxxxxxxxxxxxxxxxxx> <E11tuni-00019k-00@xxxxxxxxxxxxxxxxxx> <19991203105517.A27004@xxxxxxxx>
On Dec 3, 10:55am, Clint Adams wrote:
} Subject: Re: PATCH: Previous zsh.yo.in patch wasn't good enough
}
} > The source tree should not be modified by the build process alone;
} > building should only modify the source tree if the source has already
} > been modified.
}
} So I don't seem to have the original PATCH: Previous zsh.yo.in patch wasn't
} good enough, nor does it seem to be on the web mailing list archives.
Original was 8857, "PATCH: zsh.yo not properly generated from zsh.yo.in"
} Why can't zsh.yo be generated in the build directory?
When zsh.yo is in the separate build directory, the zsh.info generated
from zsh.texi is empty except for the comment that it was generated by
makeinfo. I tried rebuilding from clean and got the same result; the
trace output from "yodl" indicated that it wasn't reading any of the
$(sdir)/Doc/Zsh/*.yo files. When I relocated zsh.yo back to the source
tree, everything worked.
Maybe there's just some include-path thing going on that I missed.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author