From: Eric Botcazou <ebotcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Subject: [Ada] Add check for sys/capability.h
Date: Mon, 22 May 2017 07:27:00 -0000 [thread overview]
Message-ID: <3562696.NdlOsQfm3r@polaris> (raw)
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
In preparation for an upcoming improvement.
Tested on x86_64-suse-linux, applied on the mainline.
2017-05-22 Eric Botcazou <ebotcazou@adacore.com>
libada/
* configure.ac: Add check for sys/capability.h header.
(have_capability): New substitution.
* configure: Regenerate.
* Makefile.in (GNATLIBCFLAGS_FOR_C): Add @have_capability@.
--
Eric Botcazou
[-- Attachment #2: p.diff --]
[-- Type: text/x-patch, Size: 988 bytes --]
Index: Makefile.in
===================================================================
--- Makefile.in (revision 248140)
+++ Makefile.in (working copy)
@@ -61,7 +61,7 @@ PICFLAG = @PICFLAG@
GNATLIBFLAGS= -W -Wall -gnatpg -nostdinc
GNATLIBCFLAGS= -g -O2
GNATLIBCFLAGS_FOR_C = -W -Wall $(GNATLIBCFLAGS) $(CFLAGS_FOR_TARGET) \
- -fexceptions -DIN_RTS @have_getipinfo@
+ -fexceptions -DIN_RTS @have_getipinfo@ @have_capability@
host_subdir = @host_subdir@
GCC_DIR=$(MULTIBUILDTOP)../../$(host_subdir)/gcc
Index: configure.ac
===================================================================
--- configure.ac (revision 248140)
+++ configure.ac (working copy)
@@ -144,6 +144,10 @@ if test x$have_unwind_getipinfo = xyes;
fi
AC_SUBST(have_getipinfo)
+# Check for <sys/capability.h>
+AC_CHECK_HEADER([sys/capability.h], have_capability=-DHAVE_CAPABILITY, have_capability=)
+AC_SUBST(have_capability)
+
# Determine what GCC version number to use in filesystem paths.
GCC_BASE_VER
reply other threads:[~2017-05-22 7:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3562696.NdlOsQfm3r@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).