From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Peter Breitenlohner" <peb@mppmu.mpg.de>, <zsh-workers@sunsite.dk>
Subject: RE: zsh-4.0.1 -- some minor build/install problems
Date: Mon, 18 Jun 2001 13:24:47 +0400 [thread overview]
Message-ID: <000c01c0f7d8$84922220$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <Pine.LNX.4.21.0106111210040.1321-200000@nbltheo1.mppmu.mpg.de>
>
> 1. zsh-4.0.1/Test/Makefile.in:
>
> without the patch "make DESTDIR=some_where check" rather badly fails.
> Why would I want to use "DESTDIR=some_where" together with "make check"?
> Seen in isolation this admittedly doesn't make much sense, nevertheless
> "make check" shouldn't fail. Consider, however,
> "make DESTDIR=some_where all check install"
>
That makes sense I guess.
> 2. zsh-4.0.1/Makefile.in:
>
> without the patch I had to say
> "make all; make -C Doc info" as user
> and "make install install.info" as root
> instead of the more natural "make all info".
> You might say that "make install.info" will build the info pages in any
> case. True, but when the build tree is on an nfs-mounted
> filesystem, root may
> not have write permission.
>
The actual bug is that currently info is not created at all when building
off CVS. install.info depends on texi not on info as it should. Your patch
does not fix it. I'll commit the right one.
There remains the issue of make install.info vs. make info of course.
> 3. zsh-4.0.1/Doc/Makefile.in:
>
> without the patch "make DESTDIR=some_where install.info" produces
> some weird
> messages (in my case zsh.info from zsh-3.0.5 had no 'INFO-DIR-SECTION', or
> there may not be any /usr/local/info/zsh.info at all).
>
Now, when I'm looking at it - DESTDIR was instroduced for package creation -
in which case install-info is pretty useless and DESTDIR is plain wrong.
Alternative would be to skip install-info if -n $DESTDIR.
-andrej
next prev parent reply other threads:[~2001-06-18 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 9:02 Peter Breitenlohner
2001-06-18 9:24 ` Andrej Borsenkow [this message]
2001-06-18 9:35 ` Andrej Borsenkow
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='000c01c0f7d8$84922220$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=peb@mppmu.mpg.de \
--cc=zsh-workers@sunsite.dk \
/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).