zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: [Bug] Strange Globing Behaviour when used with sudo
Date: Thu, 31 May 2018 09:44:03 +0100	[thread overview]
Message-ID: <20180531084405eucas1p1f7d75b7d276162789e772df0ccb4997b~zrjXkgfW60483504835eucas1p1G@eucas1p1.samsung.com> (raw)
In-Reply-To: <CAMaoPXwFdVPszgra5busqtLNqAKsJxDV56LPW9ZrtUbg=tbSMQ@mail.gmail.com>

On Wed, 30 May 2018 22:49:32 +0200
Bengt Brodersen <bengt.brodersen@gmail.com> wrote:
> Just found a paragraph in stat(2) manpage on macos

If I've read this correctly, it sounds like it's worth trying to

#define _DARWIN_NO_64_BIT_INODE

in the zsh configuration just to see what happens (and then "make
clean" and "make").  This should have one of two effects (i) ino_t
becomes 32 bits, which works around (but does not properly fix) the
problem (ii) the compilation will fail because 32-bit sizes aren't
available in that configuration, which doesn't confirm this is
necessarily a problem but might be a hint.

If it is the issue, it's going to take some detective work by someone on
MacOS as grepping the code doesn't reveal an obviously missing use of
ino_t in the zsh code --- worth checking if ino_t is actually
correctly typedef'd.

If that's not the issue, then back to the drawing board.

pws


  reply	other threads:[~2018-05-31  8:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 17:11 Bengt Brodersen
2018-05-30 18:06 ` Bart Schaefer
2018-05-30 19:15   ` Daniel Shahaf
2018-05-30 20:23     ` Phil Pennock
2018-05-30 20:44       ` Bengt Brodersen
2018-05-30 20:49         ` Bengt Brodersen
2018-05-31  8:44           ` Peter Stephenson [this message]
     [not found]           ` <20180531094403.05b62bee@camnpupstephen.cam.scsc.local>
2018-05-31  8:49             ` Peter Stephenson
2018-05-31 11:39               ` Jun T
2018-05-31 15:29                 ` Peter Stephenson
2018-05-31 18:15                   ` Daniel Tameling
2018-06-01 14:08                     ` Jun T.
2018-06-02 18:17                       ` Daniel Tameling
2018-06-03 16:30                         ` Jun T.
2018-06-03 18:48                           ` Daniel Tameling
2018-06-03 19:17                             ` dana
2018-06-04  1:23                               ` Jun T
2018-06-04 12:48                           ` Jun T
2018-06-14 12:26           ` Bengt Brodersen
2018-05-31  6:37       ` Martijn Dekker

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='20180531084405eucas1p1f7d75b7d276162789e772df0ccb4997b~zrjXkgfW60483504835eucas1p1G@eucas1p1.samsung.com' \
    --to=p.stephenson@samsung.com \
    --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).