From: Nick Clifton <nickc@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1
Date: Fri, 15 Jun 2018 14:58:00 -0000 [thread overview]
Message-ID: <2845ca26-32ad-5b7f-0872-bff6c062cbe0@redhat.com> (raw)
In-Reply-To: <eeeca5ba-4f35-7deb-78fc-3eb73bf6f31a@ericsson.com>
Hi Simon,
>> Also the config/override.m4 file still contains a hard coded requirement
>> for autoconf 2.64 exactly.
>
> Are you talking about this?
>
> dnl Fix 2.64 cross compile detection for AVR and RTEMS
> dnl by not trying to compile fopen.
> m4_if(m4_defn([m4_PACKAGE_VERSION]), [2.64],
> [m4_foreach([_GCC_LANG], [C, C++, Fortran, Fortran 77],
> [m4_define([_AC_LANG_IO_PROGRAM(]_GCC_LANG[)], m4_defn([AC_LANG_PROGRAM(]_GCC_LANG[)]))])])
Nope - this:
dnl Ensure exactly this Autoconf version is used
m4_ifndef([_GCC_AUTOCONF_VERSION],
[m4_define([_GCC_AUTOCONF_VERSION], [2.64])])
Around line 30 in <binutils-src>/config/override.m4.
Cheers
Nick
next prev parent reply other threads:[~2018-06-15 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 0:43 Simon Marchi
2018-06-15 0:46 ` [PATCH 2/2] Generated files Simon Marchi
2018-06-15 3:00 ` Simon Marchi
2018-06-15 14:22 ` [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1 Nick Clifton
2018-06-15 14:38 ` Simon Marchi
2018-06-15 14:58 ` Nick Clifton [this message]
2018-06-15 15:14 ` Simon Marchi
2018-06-15 15:30 ` Nick Clifton
2018-06-15 15:38 ` Simon Marchi
2018-06-15 15:54 ` Nick Clifton
2018-06-16 1:39 ` Alan Modra
2018-06-16 3:56 ` Simon Marchi
2018-06-16 7:17 ` Andreas Schwab
2018-06-18 2:46 ` Alan Modra
2018-06-18 3:05 ` Simon Marchi
2018-06-18 9:42 ` Nick Clifton
2018-06-15 17:29 ` Joseph Myers
2018-06-16 3:05 ` Simon Marchi
2018-06-18 15:12 ` Joseph Myers
2018-06-18 15:32 ` Simon Marchi
2018-06-16 22:41 ` Andreas K. Huettel
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=2845ca26-32ad-5b7f-0872-bff6c062cbe0@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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