zsh-users
 help / color / mirror / code / Atom feed
From: Jim <linux.tech.guy@gmail.com>
To: zsh <zsh-users@zsh.org>
Subject: Re: Zsh requires Bash? 2002 revisited
Date: Sun, 7 Jan 2018 14:41:05 -0600	[thread overview]
Message-ID: <CA+rB6GLzDq71DXHqLF4+F9vS49BSJsHuVTuR80zrKFbpPWMKkw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZWFZoK0Fo4J4vua3cfZPVySLgUFUWWaYtu7M1Vynuv3Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2102 bytes --]

On Sat, Jan 6, 2018 at 2:57 PM, Bart Schaefer <schaefer@brasslantern.com>
wrote:

> 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"?
>

After reading the other posts in this thread, I don't believe the following
is all that relevant any more, but just in case.

The man page for posh does not list "rm" as one of its builtins. Nor does it
have "mv". So most likely, not here.?

"make -k" also fails.


> 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).
>

Looks like Src/mkmakemod.sh is called at least four times. This is where
stamp-modobjs.tmp is supposed to get created.  Then Src/Makefile.in
does a cmp of stamp-modobjs and stamp-modobjs.tmp. If they compare
it removes stamp-modobjs.tmp, if not it moves stamp-modobjs.tmp to
stamp-modobjs. When moved it also outputs the message
"Updated `stamp-modobjs", which is happening.  Then later the message
"cat: stamp-modobjs: No such file or directory" is output indicating the
file
isn't there.  Trying to figure out what happens in between. Neither file is
present when make exits. A normal exit by the other shells, has at least
stamp-modobjs present.


> 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.
>

If its still of any interest, attached is the compressed diff comparing
bash vs posh
outputs of config.log. Mail bounced my previous post with the uncompressed
file attached(to large).

If you need any more info, I will try to get you what you need. For now I
have a
couple of versions of zsh to compile, sans posh.

Jim Murphy

[-- Attachment #1.2: Type: text/html, Size: 3287 bytes --]

[-- Attachment #2: config.log-diff.xz --]
[-- Type: application/x-xz, Size: 9048 bytes --]

  reply	other threads:[~2018-01-07 20:41 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
2018-01-07 20:41       ` Jim [this message]
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=CA+rB6GLzDq71DXHqLF4+F9vS49BSJsHuVTuR80zrKFbpPWMKkw@mail.gmail.com \
    --to=linux.tech.guy@gmail.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).