public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] [testsuite] Pass pthreads in prepare_for_testing
Date: Wed, 22 Nov 2017 17:26:00 -0000 [thread overview]
Message-ID: <1daad298d699383bb4f35aa919a1acfa0ab8e16c@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 1daad298d699383bb4f35aa919a1acfa0ab8e16c ***
Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: 1daad298d699383bb4f35aa919a1acfa0ab8e16c
[testsuite] Pass pthreads in prepare_for_testing
"pthreads" in the right flag to pass in prepare_for_testing to linker,
instead of additional_flags. Without this patch, the test case can't be
complied by clang.
gdb compile failed, clang: warning: -lpthread: 'linker' input unused
gdb/testsuite:
2017-11-22 Yao Qi <yao.qi@linaro.org>
* gdb.base/info-os.exp: Pass pthreads.
* gdb.multi/multi-attach.exp: Likewise.
next reply other threads:[~2017-11-22 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 17:26 sergiodj+buildbot [this message]
2017-11-22 17:26 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-11-22 19:19 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-11-22 19:27 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-11-22 19:35 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-22 19:57 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-11-22 20:16 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-11-22 21:16 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-11-22 21:46 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-11-22 22:53 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-22 23:18 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-11-22 23:42 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
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=1daad298d699383bb4f35aa919a1acfa0ab8e16c@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@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).