From: Kai Tietz <ktietz70@googlemail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, terry.gua@arm.com
Subject: Re: [patch]: Fix Bug 65038 - [regression 5] Unable to find ftw.h for libgcov-util.c
Date: Fri, 27 Feb 2015 14:40:00 -0000 [thread overview]
Message-ID: <CAEwic4YKu=yaCU0A92st24zUstk6wLDtroyek9mYoXB7ACzHKw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoTE1VtqSc_DLdY3TTX8ByykLS2L51nX6xecpJqexeWLw@mail.gmail.com>
2015-02-27 14:48 GMT+01:00 H.J. Lu <hjl.tools@gmail.com>:
> On Thu, Feb 26, 2015 at 6:49 AM, Kai Tietz <ktietz70@googlemail.com> wrote:
>> Hi,
>>
>> This is the remaining fix for re-enabling native boostrap for
>> Windows-variant of gcc without disabling -Werror for libgcc.
>>
>> ChangeLog
>>
>> 2015-02-26 Kai Tietz <ktietz@redhat.com>
>>
>> PR target/65038
>> * config.in: Regenerated.
>> * configure: Likewise.
>> * configure.ac (AC_HEADER_STDC): Add explicit.
>> (AC_CHECK_HEADERS): Check for default headers
>> plus for ftw.h one.
>> * libgcov-util.c (gcov_read_profile_dir): Disable use
>> of ftw-function, if header not found.
>> (ftw_read_file): Don't translate if ftw header isn't
>> present.
>>
>> Regression-tested for x86_64-unknown-linux-gnu. Bootstrapped for
>> i686-pc-mingw32.
>> I will apply soon, if there are no objections.
>
> I believe it breaks bootstrap on Linux/x86:
>
> https://gcc.gnu.org/ml/gcc-regression/2015-02/msg00580.html
>
> --
> H.J.
Already fixed. See bug
--
Kai
prev parent reply other threads:[~2015-02-27 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 14:58 Kai Tietz
2015-02-27 13:31 ` Kai Tietz
2015-02-27 14:13 ` H.J. Lu
2015-02-27 14:40 ` Kai Tietz [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='CAEwic4YKu=yaCU0A92st24zUstk6wLDtroyek9mYoXB7ACzHKw@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=terry.gua@arm.com \
/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).