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] Fix various tests to use -no-pie linker flag when needed
Date: Fri, 21 Dec 2018 21:16:00 -0000	[thread overview]
Message-ID: <6e8b1ab2fd4c692146eb14295866920f83dc5403@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 6e8b1ab2fd4c692146eb14295866920f83dc5403 ***

Author: Jan Vrany <jan.vrany@fit.cvut.cz>
Branch: master
Commit: 6e8b1ab2fd4c692146eb14295866920f83dc5403

Fix various tests to use -no-pie linker flag when needed

Various tests use test code written in i386 / x86_64 assembly that cannot
be used to create PIE executables. Therefore compilation of test programs
failed on systems where the compiler default is to create PIE executable.

The solution is to use -no-pie linker flag, however, such flag may not
(is not) supported by all compilers GDB needs to support (e.g. gcc 4.8).
To handle this, introduce a new flag to gdb_compile - nopie - which
inserts -no-pie linker flag where supported and is no-op where it is
not. By default, -no-pie flag is inserted since most modern compiler do
support it.


             reply	other threads:[~2018-12-21 21:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 21:16 sergiodj+buildbot [this message]
2018-12-21 21:25 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-12-22  2:37 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-12-22  3:06 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-12-22  4:09 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-12-22  4:09 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-12-22  4:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-12-22  4:31 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-12-22  4:47 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-12-22  4:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-12-22  4:59 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-12-22 10:39 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-12-22 10:51 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " sergiodj+buildbot
2018-12-22 11:11 ` Failures on Ubuntu-Aarch64-m64, " 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=6e8b1ab2fd4c692146eb14295866920f83dc5403@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).