From: Alan Modra <amodra@gmail.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Martin Sebor <msebor@redhat.com>, Andreas Schwab <schwab@suse.de>,
Jeff Law <law@redhat.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] target/65286 - Disable multilib for ppc64le
Date: Tue, 10 Mar 2015 07:28:00 -0000 [thread overview]
Message-ID: <20150310072844.GD11451@bubble.grove.modra.org> (raw)
In-Reply-To: <20150310061348.GA342@x4>
On Tue, Mar 10, 2015 at 07:13:48AM +0100, Markus Trippelsdorf wrote:
> This patch breaks the build on ppc64le:
Works for me with your configure options.
> trippels@gcc2-power8 gcc_build_dir % ../gcc/configure --with-cpu=power8 --disable-libsanitizer --disable-bootstrap --disable-libstdcxx-pch --disable-libvtv --disable-libitm --disable-libcilkrts --disable-libssp --disable-libgomp --disable-werror --disable-multilib --enable-languages=c,c++
At a guess, you're trying to build without glibc installed. If so,
you'll also need --disable-shared. I'm a bit surprised if you could
do that before my patch.
> There is a ppc64le compile farm machine available @gcc2-2-power8.osuosl.org.
I would be greedy to load the compile farm when I can use internal IBM
machines. :)
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2015-03-10 7:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 0:59 Martin Sebor
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 [this message]
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=20150310072844.GD11451@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=markus@trippelsdorf.de \
--cc=msebor@redhat.com \
--cc=schwab@suse.de \
/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).