This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH COMMITTED] check-wrapper-headers test: Adjust Fortran include file directory
- From: Florian Weimer <fweimer at redhat dot com>
- To: Zack Weinberg <zackw at panix dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 07 Mar 2019 18:24:16 +0100
- Subject: Re: [PATCH COMMITTED] check-wrapper-headers test: Adjust Fortran include file directory
- References: <20190307163306.B3E8F81D9FFB@oldenburg2.str.redhat.com> <CAKCAbMhhFxXvOtBRZGzWZvb=e7MULRU-QsgMCiqUMf-vZFb7Wg@mail.gmail.com>
* Zack Weinberg:
> On Thu, Mar 7, 2019 at 11:33 AM Florian Weimer <fweimer@redhat.com> wrote:
>>
>> 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.
>
> For future-proofing, the script should do both checks:
>
> if header.startswith("finclude/") or "/finclude/" in header:
>
> (I'm working on a patch series which, among other things, removes all
> of the installed headers from the top-level include directory.)
This is the relative installed path, relative to the include directory,
which is put into the headers make variable.
I expect that Fortran headers will live exclusively in
/usr/include/finclude, which is why I'm not checking for finclude
subdirectories.
Thanks,
Florian