From: Oliver Kiddle <opk@zsh.org>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: build from source
Date: Fri, 02 Feb 2024 18:08:39 +0100 [thread overview]
Message-ID: <11804-1706893719.193399@QYHM.FK8t.SZbG> (raw)
In-Reply-To: <e00e33a9-c9be-49bc-b007-c17c161c31f0@eastlink.ca>
Ray Andrews wrote:
>
> The 'C02' test reports the same error. I'm tempted to fiddle with a copy of
> the test and see just what's going on there. I doubt anything is really
> broken, as you say.
It is fairly easy to replicate. Use stat to examine the timestamps. The
test is reliant on the underlying filesystem. I know to avoid builds in
my home directory which is typically NFS and prefer a local scratch
filesystem which will also be faster. Use df -T . to see the type of
filesystem for the current directory.
> /bin/sh: 4: makeinfo: not found
> make[1]: *** [Makefile:498: install.info] Error 1
> make[1]: Leaving directory '/aWorking/Zsh/zsh-5.9/Doc'
> make: *** [Makefile:255: install.info] Error 2
>
> Debian has no such thing as 'makeinfo' but it does have 'install-info' and file
> 'INSTALL' does say:
apt install texinfo
Debian's website has a very useful feature for searching by file
contents.
https://packages.debian.org/cgi-bin/search_contents.pl?word=makeinfo&searchmode=searchfiles&case=insensitive&version=unstable&arch=i386
Or you can install and setup command-not-found
For building zsh (or anything) from source, getting all the dependencies
installed tends to be easier than digging into Makefiles to skip
non-essentials.
It'd be really good to get more testing of the current git head. There
have been quite a few changes and it'd be good to find any regressions
before a release.
Oliver
next prev parent reply other threads:[~2024-02-02 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 22:31 Ray Andrews
2024-02-01 23:15 ` Bart Schaefer
2024-02-02 1:36 ` Ray Andrews
2024-02-02 2:08 ` Bart Schaefer
2024-02-02 16:14 ` Ray Andrews
2024-02-02 17:08 ` Oliver Kiddle [this message]
2024-02-02 18:13 ` Ray Andrews
2024-02-02 23:06 ` Ray Andrews
2024-02-03 22:27 ` Bart Schaefer
2024-02-03 23:42 ` Ray Andrews
2024-02-04 1:26 ` Lawrence Velázquez
2024-02-04 2:00 ` Ray Andrews
2024-02-02 6:00 ` Lawrence Velázquez
2024-02-02 16:30 ` Ray Andrews
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=11804-1706893719.193399@QYHM.FK8t.SZbG \
--to=opk@zsh.org \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@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).