SUPERH platform development
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: linux-sh@vger.kernel.org
Subject: Re: Bug#775611: [sh]: FTBFS due to unknown compiler option '-m32'
Date: Sun, 18 Jan 2015 09:58:15 +0000	[thread overview]
Message-ID: <1421575095.31046.99.camel@decadent.org.uk> (raw)

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

On Sun, 2015-01-18 at 00:35 +0100, John Paul Adrian Glaubitz wrote:
> Package: linux
> Version: 3.16.7-ckt4-1
> Severity: normal
> Tags: patch
> 
> Hi!
> 
> The kernel package currently fails to build from source on sh4 since
> the build scripts try to pass the '-m32' compiler option on gcc which
> is not available with gcc on sh4 (also according to the manpage).
> 
> Selecting HAVE_C_RECORDMCOUNT in arch/sh/Kconfig (see attached patch
> by Ben Hutchings) fixes the issues. However, I also suggest removing
> the line "$cc .= " -m32";" for sh compiler options in scripts/
> recordmcount.pl.

Steven and SH experts, what do you think of this?

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

             reply	other threads:[~2015-01-18  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18  9:58 Ben Hutchings [this message]
2015-01-18 11:15 ` Bug#775611: [sh]: FTBFS due to unknown compiler option '-m32' Geert Uytterhoeven
2015-01-18 11:52 ` Ben Hutchings
2015-01-18 12:59 ` John Paul Adrian Glaubitz

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=1421575095.31046.99.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=linux-sh@vger.kernel.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