zsh-workers
 help / color / mirror / code / Atom feed
From: Alexander Kapshuna <kapsh@kap.sh>
To: Peter Stephenson <p.stephenson@samsung.com>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Failing test for 5.5: C03traps, W02jobs
Date: Tue, 10 Apr 2018 20:16:32 +0300	[thread overview]
Message-ID: <3128331523380592@web45j.yandex.ru> (raw)
In-Reply-To: <20180410174547.0834141e@camnpupstephen.cam.scsc.local>

Yes, you are right. I am using glibc 2.27. 
Applying this patch fixes both of fails. Thanks for the help. 

./configure warns though about:

> checking where signal.h is located... ./configure: line 8998: test: too many arguments
>  /usr/x86_64-pc-linux-gnu/include/bits/signum.h /usr/x86_64-pc-linux-gnu/include/bits/signum-generic.h

But it seems to be harmless.


Can somebody also tell, is there any chance to see this fix in the close future? Something like hotfix release 5.5.1.

-- 
Alexander "kapsh" Kapshuna
kapsh@kap.sh


10.04.2018, 19:46, "Peter Stephenson" <p.stephenson@samsung.com>:
> On Tue, 10 Apr 2018 19:18:30 +0300
> Александр Капшуна <kapsh@kap.sh> wrote:
>>  I was trying to build a brand new zsh 5.5 but `make test` finished
>>  with two failures. Several people also reported one or both of this
>>  fails.
>
> Signal names not recognised --- I would guess this is down to the change
> in glibc 2.25 reported (and fixed) by Benedikt Morbach in
> zsh-workers/42618?
>
> pws



  reply	other threads:[~2018-04-10 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180410163106epcas5p4219272adac67653e93442e97285597a0@epcas5p4.samsung.com>
2018-04-10 16:18 ` Александр Капшуна
2018-04-10 16:45   ` Peter Stephenson
2018-04-10 17:16     ` Alexander Kapshuna [this message]
2018-04-11  9:26       ` Peter Stephenson
2018-04-11 12:43       ` Axel Beckert

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=3128331523380592@web45j.yandex.ru \
    --to=kapsh@kap.sh \
    --cc=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).