From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: linux-api@vger.kernel.org, libc-alpha@sourceware.org,
linuxppc-dev@lists.ozlabs.org, adhemerval.zanella@linaro.org,
hpa@zytor.com
Subject: Re: [PATCH] Linux: Define struct termios2 in <termios.h> under _GNU_SOURCE [BZ #10339]
Date: Wed, 17 Apr 2019 21:22:27 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1904172121500.14148@digraph.polyomino.org.uk> (raw)
In-Reply-To: <875zrnlakd.fsf@oldenburg2.str.redhat.com>
On Tue, 9 Apr 2019, Florian Weimer wrote:
> diff --git a/sysdeps/unix/sysv/linux/Makefile b/sysdeps/unix/sysv/linux/Makefile
> index 52ac6ad484..4cb5e4f0d2 100644
> --- a/sysdeps/unix/sysv/linux/Makefile
> +++ b/sysdeps/unix/sysv/linux/Makefile
> @@ -156,6 +156,7 @@ endif
>
> ifeq ($(subdir),termios)
> sysdep_headers += termio.h
> +tests += tst-termios2
> endif
This is missing the addition of bits/termios2-struct.h to the installed
headers.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2019-04-17 21:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 10:47 [PATCH] Linux: Define struct termios2 in <termios.h> under _GNU_SOURCE [BZ #10339] Florian Weimer
2019-04-09 15:02 ` hpa
2019-04-10 6:50 ` Florian Weimer
2019-04-15 15:54 ` hpa
2019-04-09 15:07 ` hpa
2019-04-09 16:04 ` Florian Weimer
2019-04-10 20:24 ` Adhemerval Zanella
2019-04-11 11:07 ` Florian Weimer
2019-04-11 12:53 ` Adhemerval Zanella
2019-04-12 7:50 ` Florian Weimer
2019-04-15 12:28 ` Florian Weimer
2019-04-15 15:53 ` hpa
2019-04-15 17:22 ` Adhemerval Zanella
2019-04-17 22:04 ` H. Peter Anvin
2019-04-18 11:09 ` Adhemerval Zanella
2019-04-18 14:46 ` hpa
2019-04-16 9:59 ` Florian Weimer
2019-04-16 12:11 ` Adhemerval Zanella
2019-04-17 22:06 ` H. Peter Anvin
2019-04-17 21:22 ` Joseph Myers [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=alpine.DEB.2.21.1904172121500.14148@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.
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).