From: Peter Stephenson <p.stephenson@samsung.com>
To: Alexander Kapshuna <kapsh@kap.sh>,
"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Failing test for 5.5: C03traps, W02jobs
Date: Wed, 11 Apr 2018 10:26:31 +0100 [thread overview]
Message-ID: <20180411102631.68c60c83@camnpupstephen.cam.scsc.local> (raw)
In-Reply-To: <3128331523380592@web45j.yandex.ru>
On Tue, 10 Apr 2018 20:16:32 +0300
Alexander Kapshuna <kapsh@kap.sh> wrote:
> 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
Some extra quotes will help with that.
> Can somebody also tell, is there any chance to see this fix in the
> close future? Something like hotfix release 5.5.1.
Yes, I'll probably do that during the next week.
pws
diff --git a/configure.ac b/configure.ac
index c0686b6..d15a6cd 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1553,12 +1553,12 @@ do
SIGNAL_H="$SIGNAL_H $SIGNAL_TRY_H"
fi
done
-if test x$SIGNAL_H = x; then
+if test "x$SIGNAL_H" = x; then
AC_MSG_ERROR(SIGNAL MACROS NOT FOUND: please report to developers)
fi
-zsh_cv_path_signal_h=$SIGNAL_H
+zsh_cv_path_signal_h="$SIGNAL_H"
])
-SIGNAL_H=$zsh_cv_path_signal_h
+SIGNAL_H="$zsh_cv_path_signal_h"
AC_SUBST(SIGNAL_H)dnl
dnl Where are error names located? Needed as input for errnames1.awk
next prev parent reply other threads:[~2018-04-11 9:26 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
2018-04-11 9:26 ` Peter Stephenson [this message]
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=20180411102631.68c60c83@camnpupstephen.cam.scsc.local \
--to=p.stephenson@samsung.com \
--cc=kapsh@kap.sh \
--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).