From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Nate Case <ncase@xes-inc.com>
Cc: linuxppc-dev@ozlabs.org, ths@linutronix.de
Subject: Re: [PATCH] powerpc: enforce a non-spe kernel build even on broken compilers
Date: Fri, 17 Oct 2008 17:01:12 +0200 [thread overview]
Message-ID: <20081017150112.GA14523@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <1224252131.7879.117.camel@localhost.localdomain>
* Nate Case | 2008-10-17 09:02:11 [-0500]:
>On Wed, 2008-10-15 at 16:43 +0200, Sebastian Andrzej Siewior wrote:
>> With this patch it compiles and boots fine.
>> The option -mabi=no-spe is not required.
>
>Please don't accept this patch yet. My past testing showed that
>"-mabi=no-spe" was required for my toolchain. I'll go back and double
>check though.
Okay. Here my compiler details:
| powerpc-linux-gnuspe-gcc -v
| Using built-in specs.
| Target: powerpc-linux-gnuspe
| Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.1-9'
| --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
| --enable-languages=c,c++,obj-c++ --prefix=/usr --enable-shared
| --with-system-zlib --libexecdir=/usr/lib --without-included-gettext
| --enable-threads=posix --enable-nls
| --with-gxx-include-dir=/usr/powerpc-linux-gnuspe/include/c++/4.3.1
| --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug
| --disable-multilib --disable-multilib --with-cpu=8540
| --enable-e500_double --with-long-double-128 --enable-checking=release
| --program-prefix=powerpc-linux-gnuspe-
| --includedir=/usr/powerpc-linux-gnuspe/include --build=i486-linux-gnu
| --host=i486-linux-gnu --target=powerpc-linux-gnuspe
| Thread model: posix
| gcc version 4.3.1 (Debian 4.3.1-9)
ths told me that we need all three options in this order because of how
they interact with gcc's internal flags.
>- Nate Case <ncase@xes-inc.com>
Sebastian
next prev parent reply other threads:[~2008-10-17 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 14:23 [PATCH] powerpc: enforce a non-spe kernel build even on broken compilers Sebastian Siewior
2008-10-14 19:25 ` Nate Case
2008-10-14 22:02 ` Nate Case
2008-10-14 21:23 ` Kumar Gala
2008-10-14 22:35 ` Nate Case
2008-10-14 22:49 ` Sebastian Andrzej Siewior
2008-10-15 8:59 ` Sebastian Andrzej Siewior
2008-10-15 13:25 ` Kumar Gala
2008-10-15 14:43 ` Sebastian Andrzej Siewior
2008-10-15 16:31 ` Kumar Gala
2008-10-17 14:02 ` Nate Case
2008-10-17 15:01 ` Sebastian Andrzej Siewior [this message]
2008-10-24 23:51 ` Nate Case
2008-10-24 23:55 ` Kumar Gala
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=20081017150112.GA14523@Chamillionaire.breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=linuxppc-dev@ozlabs.org \
--cc=ncase@xes-inc.com \
--cc=ths@linutronix.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 NNTP newsgroup(s).