All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Paul Burton <paul.burton@mips.com>
Cc: kernelci@groups.io
Subject: MIPS build failures in kernelCI
Date: Mon, 28 Jan 2019 15:44:02 +0100	[thread overview]
Message-ID: <7hpnsgrgel.fsf@baylibre.com> (raw)

Hi Paul,

We're having various build failures for a handful of defconfigs with
linux-next and mainline:

Go to one of these views, and click on "Failed":
mainline: https://kernelci.org/build/mainline/branch/master/kernel/v5.0-rc4/

Some of those defconfig targets (decstation_defconfig,
jmr3927_defconfig) are failing with:

     cc1: error: '-march=r3900' requires '-mfp32'

We're trying to use standard debian compilers for all targets, and for
MIPS we're using: mips-linux-gnu-gcc (Debian 7.4.0-1) 7.4.0

The other build failures seem to be failing because there is no make
target for uImage.gz (which we set as the default target for MIPS.)

We don't currently have a good way to have different make targets for
different defconfigs.

Switching to linux-next:
 https://kernelci.org/build/next/branch/master/kernel/next-20190125/

There are a few more build failures that seem to be missig some tools:

   ./arch/mips/tools/elf-entry: Command not found

This smells like a build step missing for the uImage.gz target?

Kevin

             reply	other threads:[~2019-01-28 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 14:44 Kevin Hilman [this message]
2019-01-28 22:39 ` MIPS build failures in kernelCI Paul Burton
2019-01-29  9:18   ` Kevin Hilman
2019-05-07 15:58   ` Kevin Hilman
2019-05-07 17:08     ` Kevin Hilman
2019-05-07 22:54       ` Paul Burton
2019-05-08 21:50         ` Kevin Hilman

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=7hpnsgrgel.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=kernelci@groups.io \
    --cc=paul.burton@mips.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.