zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: linuxtechguy@gmail.com
Cc: zsh <zsh-users@zsh.org>
Subject: Re: Zsh requires Bash? 2002 revisited
Date: Sat, 6 Jan 2018 12:57:41 -0800	[thread overview]
Message-ID: <CAH+w=7ZWFZoK0Fo4J4vua3cfZPVySLgUFUWWaYtu7M1Vynuv3Q@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6G+urH8g4TTNji44CS5jc5hqa+=Uuc=xxCzB1ggHW2XOgg@mail.gmail.com>

On Sat, Jan 6, 2018 at 12:36 PM, Jim <linux.tech.guy@gmail.com> wrote:
>
> Last lines of make:

Given that you're not seeing shell syntax errors or the like, my guess
is that posh is mishandling the -e command line option (errexit) and
causing some branches of make to fail prematurely.  Or, posh has rm as
a built-in and that's mishandling the -f option.  Try building with
"make -k"?

If it's the "rm" problem, there are two places in Makefile.in
./Src/Makefile.in:    rm -f stamp-modobjs.tmp
./Src/Makefile.in:    rm -f stamp-modobjs stamp-modobjs.tmp
where you can try "[ -f stamp-modobjs.tmp ] && rm ..." (you'll have to
split the latter of the above into two separate "rm" calls).

If that still fails it might help to see a diff of config.log from
bash vs. posh, but it seems much more likely that it's make that's
giving up here.


  reply	other threads:[~2018-01-06 20:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-06 13:47 Jim
2018-01-06 17:23 ` Bart Schaefer
2018-01-06 20:36   ` Jim
2018-01-06 20:57     ` Bart Schaefer [this message]
2018-01-07 20:41       ` Jim
2018-01-06 21:21     ` Martijn Dekker
     [not found]     ` <4e96813d-3762-da35-f681-2546c0265982__30442.5932620235$1515274776$gmane$org@inlv.org>
2018-01-07  8:10       ` Stephane Chazelas
2018-01-07 20:40         ` Bart Schaefer
2018-01-07  8:48       ` Stephane Chazelas
2018-01-07 15:14         ` Stephane Chazelas

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='CAH+w=7ZWFZoK0Fo4J4vua3cfZPVySLgUFUWWaYtu7M1Vynuv3Q@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=linuxtechguy@gmail.com \
    --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).