From: "Dmitry V. Levin" <ldv@altlinux.org>
To: elfutils-devel@sourceware.org
Subject: Re: [PATCH] tests: check gcc
Date: Tue, 21 May 2019 07:25:00 -0000 [thread overview]
Message-ID: <20190521072523.GA3310@altlinux.org> (raw)
In-Reply-To: <1558422031-165113-1-git-send-email-mingli.yu@windriver.com>
On Tue, May 21, 2019 at 03:00:31PM +0800, mingli.yu@windriver.com wrote:
> From: Mingli Yu <Mingli.Yu@windriver.com>
>
> Both run-disasm-x86-64.sh and run-disasm-x86.sh
> need gcc, so check gcc before run the test.
There are several dozens more tests that invoke gcc,
why these two need a check?
--
ldv
next prev parent reply other threads:[~2019-05-21 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 7:01 mingli.yu
2019-05-21 7:25 ` Dmitry V. Levin [this message]
2019-05-21 7:34 ` [PATCH v2] skip the test when gcc not deployed mingli.yu
2019-05-23 11:28 ` Mark Wielaard
2019-05-24 6:41 ` Yu, Mingli
2019-05-24 7:03 ` Mark Wielaard
2019-05-24 7:12 ` Yu, Mingli
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=20190521072523.GA3310@altlinux.org \
--to=ldv@altlinux.org \
--cc=elfutils-devel@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).