unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: libc-alpha@sourceware.org
Subject: [PATCH COMMITTED] check-wrapper-headers test: Adjust Fortran include file directory
Date: Thu, 07 Mar 2019 17:33:06 +0100	[thread overview]
Message-ID: <20190307163306.B3E8F81D9FFB@oldenburg2.str.redhat.com> (raw)

The check for "/finclude/" fails with the actual location of
Fortran headers because they are now stored in the "finclude"
subdirectory of the top-level include directory, so a relative path
does not contain a slash '/' before the "finclude" string.

2019-03-07  Florian Weimer  <fweimer@redhat.com>

	* scripts/check-wrapper-headers.py (check_headers): Adjust Fortran
	header check.

diff --git a/scripts/check-wrapper-headers.py b/scripts/check-wrapper-headers.py
index dc9fd86063..bae99c14c7 100644
--- a/scripts/check-wrapper-headers.py
+++ b/scripts/check-wrapper-headers.py
@@ -76,7 +76,7 @@ def check_headers(args):
         is_nonsysdep_header = os.access(header, os.R_OK)
         if is_nonsysdep_header:
             # Skip Fortran header files.
-            if '/finclude/' in header:
+            if header.startswith("finclude/"):
                 continue
 
             include_path = os.path.join(args.root, INCLUDE, header)

             reply	other threads:[~2019-03-07 16:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 16:33 Florian Weimer [this message]
2019-03-07 17:17 ` [PATCH COMMITTED] check-wrapper-headers test: Adjust Fortran include file directory Zack Weinberg
2019-03-07 17:24   ` Florian Weimer
2019-03-07 17:29     ` Zack Weinberg

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190307163306.B3E8F81D9FFB@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.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).