public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@redhat.com>
To: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: [PATCH] target/65286 - Disable multilib for ppc64le
Date: Wed, 04 Mar 2015 00:59:00 -0000	[thread overview]
Message-ID: <54F658DB.6030200@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 113 bytes --]

The attached patch resolves PR 65286 by adding --disable-multilib
when configuring for a ppc64le target.

Martin

[-- Attachment #2: gcc-65286.diff --]
[-- Type: text/x-patch, Size: 1754 bytes --]

diff --git a/ChangeLog b/ChangeLog
index bd43281..46ec13d 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2015-03-03 Martin Sebor  <msebor@redhat.com>
+
+	PR target/65286
+	* configure.ac (powerpc64le-*): Disable multilib.
+	* configure: Regenerate.
+
 2015-03-13  Jeff Law  <law@redhat.com>
 
 	* MAINTAINERS: Remove Paul Brook as a Fortran and ARM
diff --git a/configure b/configure
index 9de7295..168bf4c 100755
--- a/configure
+++ b/configure
@@ -7378,6 +7378,15 @@ if test x${is_cross_compiler} = xyes ; then
   target_configargs="--with-cross-host=${host_noncanonical} ${target_configargs}"
 fi
 
+# There is no multilib support on ppc64le.  Disable it unless it's
+# explicitly enabled.
+case "$target:$have_compiler:$enable_multilib" in
+  powerpc64le-*:yes:)
+    target_configargs="--disable-multilib ${target_configargs}"
+    enable_multilib=no
+    ;;
+esac
+
 # Special user-friendly check for native x86_64-linux build, if
 # multilib is not explicitly enabled.
 case "$target:$have_compiler:$host:$target:$enable_multilib" in
diff --git a/configure.ac b/configure.ac
index 00f7452..5ad3211 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3021,6 +3021,15 @@ if test x${is_cross_compiler} = xyes ; then
   target_configargs="--with-cross-host=${host_noncanonical} ${target_configargs}"
 fi
 
+# There is no multilib support on ppc64le.  Disable it unless it's
+# explicitly enabled.
+case "$target:$have_compiler:$enable_multilib" in
+  powerpc64le-*:yes:)
+    target_configargs="--disable-multilib ${target_configargs}"
+    enable_multilib=no
+    ;;
+esac
+
 # Special user-friendly check for native x86_64-linux build, if
 # multilib is not explicitly enabled.
 case "$target:$have_compiler:$host:$target:$enable_multilib" in

             reply	other threads:[~2015-03-04  0:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  0:59 Martin Sebor [this message]
2015-03-04 13:20 ` Segher Boessenkool
2015-03-04 13:43 ` Andreas Schwab
2015-03-04 16:19   ` Jeff Law
2015-03-04 16:40     ` Martin Sebor
2015-03-04 16:47       ` Jeff Law
2015-03-04 17:17       ` Andreas Schwab
2015-03-04 20:22         ` Martin Sebor
2015-03-05  4:06           ` Alan Modra
2015-03-05 23:14             ` Alan Modra
2015-03-09 18:00               ` David Edelsohn
2015-03-10  6:13                 ` Markus Trippelsdorf
2015-03-10  7:28                   ` Alan Modra
2015-03-10  7:33                     ` Markus Trippelsdorf
2015-03-10  7:56                       ` Jakub Jelinek
2015-03-10 11:08                         ` Markus Trippelsdorf
2015-03-10 12:06                           ` Alan Modra
2015-03-10 12:10                             ` Jakub Jelinek
2015-03-10 13:27                               ` David Edelsohn

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=54F658DB.6030200@redhat.com \
    --to=msebor@redhat.com \
    --cc=gcc-patches@gcc.gnu.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).