From: Vin Shelton <acs@alumni.princeton.edu>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Install Failure
Date: Thu, 6 Sep 2018 18:18:19 -0400 [thread overview]
Message-ID: <CACeGjnWrsDwkOtZCkvW-9rDwtX0eyhqkNJKAgYg33wWfX01tAQ@mail.gmail.com> (raw)
In-Reply-To: <1536271038.4025623.1499512728.307A5091@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
Yes, completely clean build from latest sources.
From the build directory:
mkdir zsh-2018-09-06
cd ./zsh-2018-09-06
pushd ../../src/zsh-2018-09-06/
./Util/preconfig
popd
../../src/zsh-2018-09-06/configure --prefix=/opt/zsh-2018-09-06
make
make install
If I had to guess, your source directory is not completely fresh and
../../../src/zsh-2018-09-06/Doc/help/* already exists.
- Vin
On Thu, Sep 6, 2018 at 5:57 PM, Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:
> This is with 85ae84e89583dfff54905c4632b03bcdc0aa1a79 and it doesn't
> happen with the commit before it, right? An out-of-tree build? And
> it's a clean build, i.e., you ran preconfig and configure?
>
> What is the actual command that failed, is it 'make foo' or 'make -C Doc
> foo' and what's foo?
>
> And how's your environment different to mine? I did test an out-of-tree
> build with that commit before I pushed it.
>
> Vin Shelton wrote on Thu, 06 Sep 2018 17:20 -0400:
> > Here's what I'm getting:
> >
> > make[1]: Entering directory '/home/opt/build/zsh-2018-09-06/Doc'
> > if test x"/opt/zsh-2018-09-06/share/zsh/5.6-dev-0/help" != x""; then \
> > /bin/sh ../../../src/zsh-2018-09-06/mkinstalldirs
> > /opt/zsh-2018-09-06/share/zsh/5.6-dev-0/help; \
> > /usr/bin/install -c -m 644 ../../../src/zsh-2018-09-06/Doc/help/*
> > /opt/zsh-2018-09-06/share/zsh/5.6-dev-0/help; \
> > while read from to; do \
> > rm -f /opt/zsh-2018-09-06/share/zsh/5.6-dev-0/help/$to || : ; \
> > ln -s $from /opt/zsh-2018-09-06/share/zsh/5.6-dev-0/help/$to; \
> > done < ../../../src/zsh-2018-09-06/Doc/help.txt; \
> > fi
> > mkdir -m 755 -p -- /opt/zsh-2018-09-06/share/zsh/5.6-dev-0/help
> > /usr/bin/install: cannot stat '../../../src/zsh-2018-09-06/Doc/help/*':
> No
> > such file or directory
> > /bin/sh: 4: cannot open ../../../src/zsh-2018-09-06/Doc/help.txt: No
> such
> > file
> > make[1]: *** [Makefile:481: install.runhelp] Error 2
> > make[1]: Leaving directory '/home/opt/build/zsh-2018-09-06/Doc'
> > make: *** [Makefile:226: install.runhelp] Error 2
> >
> > Source = /opt/src/zsh-2018-09-06
> > Build = /opt/build/zsh-2018-09-06
> > config.log available upon request
> >
> > - Vin
>
next prev parent reply other threads:[~2018-09-06 22:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 21:20 Vin Shelton
2018-09-06 21:57 ` Daniel Shahaf
2018-09-06 22:18 ` Vin Shelton [this message]
2018-09-07 0:06 ` Daniel Shahaf
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=CACeGjnWrsDwkOtZCkvW-9rDwtX0eyhqkNJKAgYg33wWfX01tAQ@mail.gmail.com \
--to=acs@alumni.princeton.edu \
--cc=d.s@daniel.shahaf.name \
--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).