From: "Kevin Hilman" <khilman@baylibre.com>
To: Paul Burton <paul.burton@mips.com>
Cc: "kernelci@groups.io" <kernelci@groups.io>
Subject: Re: MIPS build failures in kernelCI
Date: Tue, 07 May 2019 08:58:13 -0700 [thread overview]
Message-ID: <7hy33ijlyi.fsf@baylibre.com> (raw)
In-Reply-To: <20190128223906.b73t4tympcpom5fl@pburton-laptop>
Hi Paul,
Paul Burton <paul.burton@mips.com> writes:
> On Mon, Jan 28, 2019 at 03:44:02PM +0100, Kevin Hilman wrote:
>> 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
>
> Thanks for the report. I've just submitted a fix for that [1], and
> assuming nobody points out a problem in the next day or so I'll apply it
> to my mips-fixes branch.
>
>> 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.
>
> Would it be an option to build the 'all' target? That typically
> generates the appropriate image for the configured platform.
Revisiting this...
Turns out that 'make all' doesn't build the uImage.gz target, which is
what's used on the pistachio_marduk (with pistachio_defconfig) so we
switched the builds back to 'make uImage.gz'.
However, that fails for a few other defconfigs where that target doesn't
work.
What's your recommendation to have this working for all defconfigs?
I'm guessing we should keep 'make all' but fix any defconfigs that are
not building the uImage.gz target?
Kevin
next prev parent reply other threads:[~2019-05-07 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 14:44 MIPS build failures in kernelCI Kevin Hilman
2019-01-28 22:39 ` Paul Burton
2019-01-29 9:18 ` Kevin Hilman
2019-05-07 15:58 ` Kevin Hilman [this message]
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=7hy33ijlyi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox