mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: powerpc-linux-gnu-gcc: error: unrecognized command line option ‘-mno-spe’
Date: Wed, 23 Jan 2019 18:41:11 -0800	[thread overview]
Message-ID: <CAHQ1cqEcMK-npMm57w8w-jVJP89nCxGcoFKaJCOmGCMs=WGcnQ@mail.gmail.com> (raw)
In-Reply-To: <20190123150153.11a91063828b62bfd89c9bdf@gmail.com>

On Wed, Jan 23, 2019 at 4:02 AM Antony Pavlov <antonynpavlov@gmail.com> wrote:
>
> Hi Sascha!
>
> I'm playing with MAKEALL script to build as many defconfigs as possible.
> My build environment is base on Debian Buster.
> Debian Buster has cross compiler for PowerPC32.
>
> Alas I have no success with debian powerpc-linux-gnu-gcc 8.2.0-2.
>
> After
>
>   CROSS_COMPILE=powerpc-linux-gnu- ./MAKEALL -a ppc
>
> the error message is:
>
>   powerpc-linux-gnu-gcc: error: unrecognized command line option ‘-mno-spe’; did you mean ‘-fno-see’?
>   powerpc-linux-gnu-gcc: error: unrecognized command line option ‘-mspe=no’; did you mean ‘-misel=no’?
>   make[2]: *** [/home/builduser/barebox/./Kbuild:40: arch/ppc/lib/asm-offsets.s] Error 1
>   make[1]: *** [/home/builduser/barebox/Makefile:832: prepare0] Error 2
>   make[1]: *** Waiting for unfinished jobs....
>   powerpc-linux-gnu-gcc: error: unrecognized command line option ‘-mno-spe’; did you mean ‘-fno-see’?
>   powerpc-linux-gnu-gcc: error: unrecognized command line option ‘-mspe=no’; did you mean ‘-misel=no’?
>   make[3]: *** [/home/builduser/barebox/scripts/Makefile.build:250: scripts/mod/empty.o] Error 1
>   make[3]: *** Waiting for unfinished jobs....
>
>
> With this linux kernel-based patch ppc build has no fail.
>
> diff --git a/arch/ppc/Makefile b/arch/ppc/Makefile
> index 05ec2438a..e575e5923 100644
> --- a/arch/ppc/Makefile
> +++ b/arch/ppc/Makefile
> @@ -1,7 +1,12 @@
>
>  CPPFLAGS += -ffixed-r14 -m32   \
>         -meabi -D __PPC__ -D CONFIG_PPC \
> -       -fno-strict-aliasing -mno-spe -mspe=no
> +       -fno-strict-aliasing
> +
> +# No SPE instruction when building kernel
> +# (We use all available options to help semi-broken compilers)
> +CPPFLAGS += $(call cc-option,-mno-spe)
> +CPPFLAGS += $(call cc-option,-mspe=no)
>
>  ifdef CONFIG_RELOCATABLE
>  CPPFLAGS += -fPIC -mrelocatable
>
>
> I have no real powerpc experience to submit this patch.
>
> Could you please comment this patch?
>

Since up until a year ago I was using Barebox on MPC8544 on a daily
basis and have some PowerPC patches I've been meaning to upstream,
I'll chime in. You wouldn't see this build failure if you were using a
PowerPC toolchain build with support for e500 enabled. AFAIK, distros
don't usually ship anything like that, but you can get a pre-build one
from here https://toolchains.bootlin.com/releases_powerpc-e500mc.html

However, I've never tried to build Barebox using a generic PowerPC
toolchain, so I don't really know for sure if having e500 support
truly matters for getting a working Barebox binary. Given that, I
don't see any harm in the change above.

Thanks,
Andrey Smirnov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2019-01-24  2:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 12:01 Antony Pavlov
2019-01-24  2:41 ` Andrey Smirnov [this message]

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='CAHQ1cqEcMK-npMm57w8w-jVJP89nCxGcoFKaJCOmGCMs=WGcnQ@mail.gmail.com' \
    --to=andrew.smirnov@gmail.com \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.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