From: "Ian Lance Taylor via gcc-patches" <gcc-patches@gcc.gnu.org>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] LFS support for libbacktrace
Date: Tue, 20 Jun 2017 23:03:00 -0000 [thread overview]
Message-ID: <CAKOQZ8yvDDebPbwJ2ywOSYd4Aiw1kKA1Q9g+pYTdUFQpk8a6dw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1706141239230.22867@zhemvz.fhfr.qr>
On Wed, Jun 14, 2017 at 3:40 AM, Richard Biener <rguenther@suse.de> wrote:
>
> This fixes the [f]open use in libgfortran. Doesn't fix the ones
> in libsanitizer because those appearantly use a copy because they
> need to rename stuff...
>
> Bootstrapped and tested on x86_64-unknown-linux-gnu, ok for trunk
> and branches?
>
> Thanks,
> Richard.
>
> 2017-06-14 Richard Biener <rguenther@suse.de>
>
> * configure.ac: Add AC_SYS_LARGEFILE.
> * config.h.in: Regenerate.
> * configure: Likewise.
This is OK everywhere.
Thanks.
Ian
prev parent reply other threads:[~2017-06-20 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 10:40 Richard Biener
2017-06-20 11:15 ` Richard Biener
2017-06-27 16:46 ` Jeff Law
2017-06-20 23:03 ` Ian Lance Taylor via gcc-patches [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=CAKOQZ8yvDDebPbwJ2ywOSYd4Aiw1kKA1Q9g+pYTdUFQpk8a6dw@mail.gmail.com \
--to=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=rguenther@suse.de \
/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).