zsh-workers
 help / color / mirror / code / Atom feed
From: Vin Shelton <ethersoft@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: new zsh build hang on sparkylinux (essentially debian test)
Date: Fri, 13 May 2016 23:20:56 -0400	[thread overview]
Message-ID: <CACeGjnXfvr0ktY40iODXXFDmyokXbwVXJOkKVeA-xZSpeCrCfw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7axhqSkWSnOZoAYcPc70MuRwV6p=6h6zt_DZ9bC0YboXg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

Dear Workers,

On Wed, May 11, 2016 at 9:57 PM, Bart Schaefer <schaefer@brasslantern.com>
 wrote:

> On May 11, 2016 6:08 PM, "Vin Shelton" <ethersoft@gmail.com> wrote:
> >
> > I just installed the most recent version of sparky linux (it is based on
> > debian testing).  I built zsh and the newly-built zsh hangs.
>
> > open("/lib/x86_64-linux-gnu/libnss_compat.so.2", O_RDONLY|O_CLOEXEC) = 11
> > read(11,
> > "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320\22\0\0\0\0\0\0"...,
> > 832) = 832
> > fstat(11, {st_mode=S_IFREG|0644, st_size=31616, ...}) = 0
>
> My best guess is that's attempting to do getpwnam() but the (simulated?)
> NSS query is not returning.
>

Thanks, Bart.

Just for the record, this actually ended up being something to do with the
compiler optimization settings.  Building with CFLAGS=-O yielded a working
zsh.

$ uname -a
Linux nuc 4.5.0-2-amd64 #1 SMP Debian 4.5.3-2 (2016-05-08) x86_64 GNU/Linux

$ gcc --version
gcc (Debian 5.3.1-17) 5.3.1 20160429

  - Vin

  reply	other threads:[~2016-05-14  3:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12  1:08 Vin Shelton
2016-05-12  1:57 ` Bart Schaefer
2016-05-14  3:20   ` Vin Shelton [this message]
2016-06-02  1:05     ` Bart Schaefer
2016-06-02 13:28       ` 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=CACeGjnXfvr0ktY40iODXXFDmyokXbwVXJOkKVeA-xZSpeCrCfw@mail.gmail.com \
    --to=ethersoft@gmail.com \
    --cc=acs@alumni.princeton.edu \
    --cc=schaefer@brasslantern.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).