From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-11-01
Date: Thu, 2 Nov 2017 11:50:11 +0100 [thread overview]
Message-ID: <20171102115011.732d1d9f@windsurf> (raw)
In-Reply-To: <27b962f2-9a22-bef6-3c51-b8e5da34cb67@free.fr>
Hello,
On Thu, 2 Nov 2017 11:26:52 +0100, Julien Boibessot wrote:
> > arc | gpm-1.20.7 | http://autobuild.buildroot.net/results/15e24f8c6a3ad2bfd198cc4fb094aeace7d1ee6a
> > arc | gpm-1.20.7 | http://autobuild.buildroot.net/results/7c24edc1af7dabd2b401e750add1eccaaab8961a
> >
>
> Build failures are due to undefined __sigemptyset(). After quick
> investigation it seems that the include file defining this macro
> (include/bits/sigset.h) is no more present in glibc-2.26.
> From glibc Changelog, file seems deleted since 2017-05-20.
>
> gpm builds fine with glibc-2.23 and uclibc-1.0.26.
> No one else is impacted ?
I believe __sigemptyset() should never have been used, it looks like an
internal function. sigemptyset() should have been used instead, and is
in fact used elsewhere in gpm:
$ grep -r sigemptyset *
src/lib/liblow.c: sigemptyset (&new_sigset);
src/lib/liblow.c: sigemptyset(&sa.sa_mask);
src/lib/liblow.c: sigemptyset(&sa.sa_mask);
src/prog/gpm-root.y: __sigemptyset(&childaction.sa_mask);
You can find some glibc 2.26 fixes for gpm at
http://lfs.phayoune.org/blfs/downloads/8.1/patches/gpm-1.20.7-glibc_2.26-1.patch.
We will probably want something more fine grained, i.e one patch per
change.
See also https://github.com/telmich/gpm/pull/20.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-02 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171102070005.79F7021D67@mail.free-electrons.com>
2017-11-02 10:26 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-11-01 Julien Boibessot
2017-11-02 10:50 ` Thomas Petazzoni [this message]
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=20171102115011.732d1d9f@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox