public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Lancelot SIX <Lancelot.Six@amd.com>
To: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Cc: lsix@lancelotsix.com
Subject: Re: [PATCH] gdb/testsuite/lib/future.exp: follow dejagnu default_target_compile
Date: Thu, 22 Sep 2022 17:55:50 +0100	[thread overview]
Message-ID: <904be0b0-4b26-4551-01b3-6fb36b08b61d@amd.com> (raw)
In-Reply-To: <fe89cdce-f114-101c-ac1f-433c3e717ca7@simark.ca>


> 
> Thanks, this is ok.

Hi,

Thanks.

I'll push this in a moment.

> 
> OOC, does this mean we can remove the "find_gcc" calls in our own
> boards?  The override in future.exp does not systematically get used
> when running on a system with an older DejaGNU, so I would guess not.


As long as we do not need the override and can use dejagnu<1.6.3, we 
should maintain the find_gcc calls in the board files.

Thanks
Lancelot.

> Simon

      reply	other threads:[~2022-09-22 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 18:26 Lancelot SIX
2022-09-05 18:30 ` Lancelot SIX
2022-09-20 14:16 ` Six, Lancelot
2022-09-22 16:26 ` Simon Marchi
2022-09-22 16:55   ` Lancelot SIX [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=904be0b0-4b26-4551-01b3-6fb36b08b61d@amd.com \
    --to=lancelot.six@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.com \
    --cc=simark@simark.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).