public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "Maciej W. Rozycki" <macro@wdc.com>, libffi-discuss@sourceware.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH libffi 2/4] Use a documented way to pass $compiler_vendor to DejaGNU
Date: Mon, 06 Apr 2020 12:00:01 -0600	[thread overview]
Message-ID: <a4e6c4058dfbd780b85bb61a8ae69e20d40783e4.camel@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.21.2004031354120.461@redsun52.ssa.fujisawa.hgst.com>

On Fri, 2020-04-03 at 23:55 +0100, Maciej W. Rozycki via Gcc-patches wrote:
> Use Autoconf substitution in the template used for extra DejaGNU site 
> configuration, which is a documented supported way to pass information 
> from the `configure' script, rather than resorting to a hack with 
> extracting an undocumented internal setting from `config.log' to pass 
> the compiler vendor to DejaGNU.  No functional change (and no risk of 
> breakage with some Autoconf version anymore).
> 
> Use AM_SUBST_NOTMAKE with the new substitution so as not to place it in 
> Makefile.in files, where it is not needed, and set the Autmoake version 
> requirement accordingly.
> ---
> Hi,
> 
>  I chose to use AM_SUBST_NOTMAKE so as not to clutter Makefile.in files 
> with the new variable as Automake does that by default.  That however 
> requires the use of Automake 1.11 or newer.  By the look of our sources 
> that shouldn't be an issue as far as I can tell, but the macro invocation 
> can be dropped along with the requirement if it would.
> 
>   Maciej
> ---
>  Makefile.am              |    3 ++-
>  configure.ac             |    2 ++
>  testsuite/lib/libffi.exp |    4 ----
>  testsuite/local.exp.in   |    1 +
>  4 files changed, 5 insertions(+), 5 deletions(-)
OK
jeff
> 


  reply	other threads:[~2020-04-06 18:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 22:55 [PATCH libffi 0/4] Robustify compiler and library path selection in the testsuite Maciej W. Rozycki
2020-04-03 22:55 ` [PATCH libffi 1/4] Use a template to pass $CC and $CXX to DejaGNU Maciej W. Rozycki
2020-04-06 17:58   ` Jeff Law
2020-04-03 22:55 ` [PATCH libffi 2/4] Use a documented way to pass $compiler_vendor " Maciej W. Rozycki
2020-04-06 18:00   ` Jeff Law [this message]
2020-04-03 22:56 ` [PATCH libffi 3/4] Make `libffi-init' use $CC_FOR_TARGET Maciej W. Rozycki
2020-04-06 18:03   ` Jeff Law
2020-04-03 22:56 ` [PATCH libffi 4/4] Correct indentation throughout `libffi-init' Maciej W. Rozycki
2020-04-06 18:01   ` Jeff Law
2020-04-14 13:59 ` [PING][PATCH libffi 0/4] Robustify compiler and library path selection in the testsuite Maciej W. Rozycki
2020-04-20 12:50 ` [PING^2][PATCH " Maciej W. Rozycki

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=a4e6c4058dfbd780b85bb61a8ae69e20d40783e4.camel@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libffi-discuss@sourceware.org \
    --cc=macro@wdc.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).