public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@dinux.eu>
To: binutils@sourceware.org
Cc: Alan Modra <amodra@gmail.com>
Subject: Re: Run more ld tests when not native
Date: Tue, 03 Jan 2017 21:16:00 -0000	[thread overview]
Message-ID: <1720592.jg0hMQ4cQ7@tpdeb> (raw)
In-Reply-To: <20170102133453.GP29355@bubble.grove.modra.org>

> diff --git a/ld/testsuite/ld-elf/audit.exp b/ld/testsuite/ld-elf/audit.exp
> index b278ec1..aad5339 100644
> --- a/ld/testsuite/ld-elf/audit.exp
> +++ b/ld/testsuite/ld-elf/audit.exp
> @@ -25,11 +25,6 @@ if ![is_elf_format] {
>      return
>  }
> 
> -# The following tests require running the executable generated by ld.
> -if ![isnative] {
> -    return
> -}
> -
With isnative check removed, shouldn't this test be skipped for embedded 
targets? In other words:
+if ![check_shared_lib_support] {
+    return
+}

Regards,
Dimitar

  parent reply	other threads:[~2017-01-03 21:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 13:35 Alan Modra
2017-01-02 16:05 ` Christophe Lyon
2017-01-03  0:29   ` Alan Modra
2017-01-03  2:36     ` Alan Modra
2017-01-11 19:22     ` Maciej W. Rozycki
2017-01-20  0:33       ` Alan Modra
2017-01-20 16:17         ` [Patch] Honor ccflags when GCC used as linker driver Jiong Wang
2017-01-22 21:18           ` Alan Modra
2017-01-23 13:51             ` [ld, testsuite] Always assemble those intermeidate .o files used later Jiong Wang
2017-01-23 13:59               ` Christophe Lyon
2017-01-23 14:27                 ` Jiong Wang
2017-01-23 14:29                   ` Christophe Lyon
2017-01-24  0:44               ` Alan Modra
2017-01-31 12:51           ` [ld, testsuite, obvious] Append $board_cflags in one more place in ld-unique/unique.exp Jiong Wang
2017-01-03 21:16 ` Dimitar Dimitrov [this message]
2017-01-03 23:06   ` Run more ld tests when not native Alan Modra
2017-01-10 19:01 ` H.J. Lu
2017-01-10 21:50   ` Alan Modra
2017-01-10 22:06     ` H.J. Lu
2017-01-11  0:56       ` Alan Modra
2017-01-11 18:40         ` H.J. Lu
2019-02-14 16:53 ` Thomas Schwinge

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=1720592.jg0hMQ4cQ7@tpdeb \
    --to=dimitar@dinux.eu \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    /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).