From: Bernhard Heckel <bernhard.heckel@intel.com>
To: qiyaoltc@gmail.com
Cc: gdb-patches@sourceware.org, brobecker@adacore.com,
Bernhard Heckel <bernhard.heckel@intel.com>
Subject: [PATCH V4 2/3] Testsuite: Fix compiling of shared libraries with ICC.
Date: Mon, 18 Apr 2016 10:07:00 -0000 [thread overview]
Message-ID: <1460974046-1281-3-git-send-email-bernhard.heckel@intel.com> (raw)
In-Reply-To: <1460974046-1281-1-git-send-email-bernhard.heckel@intel.com>
We are missing "-fpic" flag when compiling shared libraries with ICC.
2016-04-18 Bernhard Heckel <bernhard.heckel@intel.com>
gdb/Testsuite/Changelog:
* lib/gdb.exp (gdb_compile_shlib): Add flag for ICC compiler.
---
gdb/testsuite/lib/gdb.exp | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 1ef6a96..75c5e68 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -3553,6 +3553,9 @@ proc gdb_compile_shlib {sources dest options} {
lappend obj_options "additional_flags=-fpic"
}
}
+ "icc-*" {
+ lappend obj_options "additional_flags=-fpic"
+ }
default {
# don't know what the compiler is...
}
--
2.7.1.339.g0233b80
next prev parent reply other threads:[~2016-04-18 10:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 10:07 [PATCH V4 0/3] fortran: Testsuite, fix different type naming across compilers Bernhard Heckel
2016-04-18 10:07 ` Bernhard Heckel [this message]
2016-04-18 10:26 ` [PATCH V4 2/3] Testsuite: Fix compiling of shared libraries with ICC Yao Qi
2016-04-18 12:18 ` [Pushed][PATCH " Heckel, Bernhard
2016-04-18 10:07 ` [PATCH V4 3/3] fortran: Testsuite, fix different type naming across compilers Bernhard Heckel
2016-04-18 10:29 ` Yao Qi
2016-04-18 12:19 ` [Pushed][PATCH " Heckel, Bernhard
2016-04-18 10:08 ` [PATCH V4 1/3] testsuite: Support detection of Intel compilers via test_compiler_version Bernhard Heckel
2016-04-18 10:26 ` Yao Qi
2016-04-18 12:17 ` [Pushed][PATCH " Heckel, Bernhard
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=1460974046-1281-3-git-send-email-bernhard.heckel@intel.com \
--to=bernhard.heckel@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).