From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Skip dlopen-libpthread.exp in cross testing
Date: Thu, 25 Sep 2014 15:38:00 -0000 [thread overview]
Message-ID: <542436DE.4030005@redhat.com> (raw)
In-Reply-To: <1411631571-30769-1-git-send-email-yao@codesourcery.com>
On 09/25/2014 08:52 AM, Yao Qi wrote:
> performed. Then I check the callers of build_executable_own_libs,
> and they are all skipped if isnative is false. It is reasonable to do
> the same in dlopen-libpthread.exp too.
Agreed.
I think we should put an "error" call in build_executable_own_libs
too, so that whoever adds the next test that uses this doesn't
end up forgetting the same thing.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-09-25 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 7:57 Yao Qi
2014-09-25 15:38 ` Pedro Alves [this message]
2014-09-28 3:51 ` Yao Qi
2014-09-29 15:28 ` Pedro Alves
2014-09-30 4:05 ` Yao Qi
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=542436DE.4030005@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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