public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Shahab Vahedi <shahab.vahedi@gmail.com>
Cc: Tom Tromey <tom@tromey.com>, gdb@sourceware.org
Subject: Re: Question about running "make check-gdb"
Date: Fri, 4 Jun 2021 14:09:43 +0100	[thread overview]
Message-ID: <20210604130943.GD2295059@embecosm.com> (raw)
In-Reply-To: <YLn44FrEKe5t2PGN@gmail.com>

* Shahab Vahedi via Gdb <gdb@sourceware.org> [2021-06-04 11:56:48 +0200]:

> Hi Tom,
> 
> Couple of days ago, you've pushed a refactoring commit [1] to gdb.
> I noticed after that change I am not able to run gdb tests for
> ARC targets anymore. I investigated a little bit and it seems like
> that the "target_alias" in generated "gdb/testsuite/site.exp" is
> not recognized correctly:
> 
> ------ After the commit -------
> $ configure --target=arc-elf32 ...
> $ make
> $ make check-gdb
> $ cat gdb/testsuite/site.exp
>   ...
>   set target_alias @target_noncanonical@
>   ...
> ------ After the commit -------
> 
> ------ Before the commit -------
> $ ./configure --target=arc-elf32 ...
> $ make
> $ make check-gdb
> $ cat gdb/testsuite/site.exp
>   ...
>   set target_alias arc-elf32
>   ...
> ------ Before the commit -------
> 
> I've tried some other target combinations as well to no avail:
> 
> $ ./configure --target=arc-none-elf32
> $ ./configure --target=arc-snps-elf
> $ ...
> 
> I would much appreciate it if you could point me in the direction of
> how to fix this.

I suspect that it was the loss of ACX_NONCANONICAL_TARGET that is the
problem, this used to be present in gdb/testsuite/configure.ac, but is
not in gdb/configure.ac.

Try adding this call into gdb/configure.ac and see if that fixes it
for you.

thanks,
Andrew

  reply	other threads:[~2021-06-04 13:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  9:56 Shahab Vahedi
2021-06-04 13:09 ` Andrew Burgess [this message]
2021-06-04 20:25   ` Tom Tromey
2021-06-04 13:54 ` Tom Tromey
2021-06-07 12:13 ` Shahab Vahedi

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=20210604130943.GD2295059@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb@sourceware.org \
    --cc=shahab.vahedi@gmail.com \
    --cc=tom@tromey.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).