From: Petr Vorel <pvorel@suse.cz>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH 3/4] travis: Remove mips builds
Date: Tue, 22 Sep 2020 11:14:48 +0200 [thread overview]
Message-ID: <20200922091448.GA45420@x230> (raw)
In-Reply-To: <20200917135032.nwkgzcnkechb5eja@tomti.i.net-space.pl>
> On Wed, Sep 09, 2020 at 10:02:20PM +0200, Petr Vorel wrote:
> > Remove mips builds fix configure error:
> > configure: error: could not force big-endian)
> Could you try to fix mips and risc5 builds instead of removing them?
mips fails due using compiler [1] which lacks lacks big-endian support:
"configure: error: could not force big-endian"
Maybe later versions (9.3.0, 10.1.0) will have the support.
The other way (probably slower) would be to add foreign architecture and install
the compiler with apt.
And also IMHO job should stop on configure fail, not continue after that.
I'll probably send a patch fixing this.
> Daniel
[1] https://mirrors.kernel.org/pub/tools/crosstool/files/bin/x86_64/8.1.0/x86_64-gcc-8.1.0-nolibc-riscv32-linux.tar.gz
next prev parent reply other threads:[~2020-09-22 9:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 20:02 [PATCH 0/4] Fix Travis CI Petr Vorel
2020-09-09 20:02 ` [PATCH 1/4] travis: Run bootstrap to fix build Petr Vorel
2020-09-17 13:41 ` Daniel Kiper
2020-09-09 20:02 ` [PATCH 2/4] travis: Fix sparc64 build Petr Vorel
2020-09-17 13:48 ` Daniel Kiper
2020-09-21 22:19 ` Petr Vorel
2020-09-22 9:05 ` Petr Vorel
2020-09-09 20:02 ` [PATCH 3/4] travis: Remove mips builds Petr Vorel
2020-09-17 13:50 ` Daniel Kiper
2020-09-17 14:17 ` Petr Vorel
2020-09-22 9:14 ` Petr Vorel [this message]
2020-10-27 19:53 ` Daniel Kiper
2020-09-09 20:02 ` [PATCH 4/4] travis: Remove riscv32 build Petr Vorel
2020-09-22 9:20 ` Petr Vorel
2020-10-27 20:06 ` Daniel Kiper
2020-12-18 4:39 ` Glenn Washburn
2020-12-18 7:55 ` Petr Vorel
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=20200922091448.GA45420@x230 \
--to=pvorel@suse.cz \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.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 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.