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 -pie in ldflags
Date: Wed, 22 Nov 2017 16:24:00 -0000	[thread overview]
Message-ID: <dc196b230b7366683799755b4461acef5cc95be7@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT dc196b230b7366683799755b4461acef5cc95be7 ***

Author: Yao Qi <yao.qi@linaro.org>
Branch: master
Commit: dc196b230b7366683799755b4461acef5cc95be7

[testsuite] Pass -pie in ldflags

-pie is a linker flag, it should be passed via "ldflags", instead
of "additional_flags".  Otherwise, clang complains,

clang: warning: argument unused during compilation: '-pie'

gdb/testsuite:

2017-11-22  Yao Qi  <yao.qi@linaro.org>

	* gdb.base/attach-pie-noexec.exp: Pass "-pie" in ldflags.
	* gdb.base/break-interp.exp: Likewise.
	* gdb.base/jit-attach-pie.exp: Likewise.


             reply	other threads:[~2017-11-22 16:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 16:24 sergiodj+buildbot [this message]
2017-11-22 16:24 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-11-22 17:12 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-11-22 17:13 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-11-22 17:17 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2017-11-22 17:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-11-22 18:05 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-11-22 18:40 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-11-22 19:14 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-22 19:38 ` Failures on Ubuntu-AArch32-native-gdbserver-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=dc196b230b7366683799755b4461acef5cc95be7@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).