From: Jack Howarth <howarth@bromo.med.uc.edu>
To: gcc-patches@gcc.gnu.org
Cc: mikestump@comcast.net, iains@gcc.gnu.org
Subject: [PATCH] Backport PR 43715 fix for darwin to gcc 4.5.1
Date: Fri, 25 Jun 2010 06:50:00 -0000 [thread overview]
Message-ID: <20100625033520.GA24847@bromo.med.uc.edu> (raw)
The attached patch backports r158747 and r158748 from gcc
trunk to gcc 4.5.1 to solve PR 43715 so that plugin support
is built on darwin. Tested on x86_64-apple-darwin10. Okay
for gcc trunk?
2010-06-24 Jack Howarth <howarth@bromo.med.uc.edu>
Backport from mainline
2010-04-21 Jack Howarth <howarth@bromo.med.uc.edu>
PR 43715
* testsuite/lib/plugin-support.exp: Use "-undefined
dynamic_lookup" on darwin.
2010-06-24 Jack Howarth <howarth@bromo.med.uc.edu>
Backport from mainline
2010-04-21 Jack Howarth <howarth@bromo.med.uc.edu>
PR 43715
* gcc/configure.ac: Use "$gcc_cv_nm -g" on darwin
instead of "$gcc_cv_objdump -T".
Use "-undefined dynamic_lookup" on darwin.
* gcc/configure: Regenerate.
Index: gcc/testsuite/lib/plugin-support.exp
===================================================================
--- gcc/testsuite/lib/plugin-support.exp (revision 161355)
+++ gcc/testsuite/lib/plugin-support.exp (working copy)
@@ -88,6 +88,10 @@
set optstr "$includes $extra_flags -DIN_GCC -fPIC -shared"
+ if { [ ishost *-*-darwin* ] } {
+ set optstr [concat $optstr "-undefined dynamic_lookup"]
+ }
+
# Temporarily switch to the environment for the plugin compiler.
restore_ld_library_path_env_vars
set status [remote_exec build "$PLUGINCC $PLUGINCFLAGS $plugin_src $optstr -o $plugin_lib"]
Index: gcc/configure.ac
===================================================================
--- gcc/configure.ac (revision 161355)
+++ gcc/configure.ac (working copy)
@@ -4544,15 +4544,23 @@
pluginlibs=
if test x"$enable_plugin" = x"yes"; then
+ case "${host}" in
+ *-*-darwin*)
+ export_sym_check="$gcc_cv_nm -g"
+ ;;
+ *)
+ export_sym_check="$gcc_cv_objdump -T"
+ ;;
+ esac
AC_MSG_CHECKING([for exported symbols])
echo "int main() {return 0;} int foobar() {return 0;}" > conftest.c
${CC} ${CFLAGS} ${LDFLAGS} conftest.c -o conftest > /dev/null 2>&1
- if $gcc_cv_objdump -T conftest | grep foobar > /dev/null; then
+ if $export_sym_check conftest | grep foobar > /dev/null; then
: # No need to use a flag
else
AC_MSG_CHECKING([for -rdynamic])
${CC} ${CFLAGS} ${LDFLAGS} -rdynamic conftest.c -o conftest > /dev/null 2>&1
- if $gcc_cv_objdump -T conftest | grep foobar > /dev/null; then
+ if $export_sym_check conftest | grep foobar > /dev/null; then
plugin_rdynamic=yes
pluginlibs="-rdynamic"
else
@@ -4572,7 +4580,14 @@
# Check that we can build shared objects with -fPIC -shared
saved_LDFLAGS="$LDFLAGS"
- LDFLAGS="$LDFLAGS -fPIC -shared"
+ case "${host}" in
+ *-*-darwin*)
+ LDFLAGS="$LDFLAGS -fPIC -shared -undefined dynamic_lookup"
+ ;;
+ *)
+ LDFLAGS="$LDFLAGS -fPIC -shared"
+ ;;
+ esac
AC_MSG_CHECKING([for -fPIC -shared])
AC_TRY_LINK(
[extern int X;],[return X == 0;],
next reply other threads:[~2010-06-25 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 6:50 Jack Howarth [this message]
2010-06-25 8:33 ` Mike Stump
2010-06-25 11:53 ` Rainer Orth
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=20100625033520.GA24847@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=iains@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).