From: Fredrik Noring <noring@nocrew.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Fam Zheng" <famz@redhat.com>,
qemu-devel@nongnu.org, "Mike Frysinger" <vapier@gentoo.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
"Jürgen Urban" <JuergenUrban@gmx.de>
Subject: Re: [Qemu-devel] [RFC PATCH 1/2] docker: Add gentoo-mipsr5900el-cross image
Date: Mon, 19 Nov 2018 16:55:48 +0100 [thread overview]
Message-ID: <20181119155548.GB2405@sx9> (raw)
In-Reply-To: <87wop9i7db.fsf@linaro.org>
Hi Alex,
> This fails to build glibc, but doesn't exactly give much info:
>
> * Log: /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-binutils.log
> * Emerging cross-binutils ... [ ok ]
> * Log: /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-linux-headers-quick.log
> * Emerging cross-linux-headers-quick ... [ ok ]
> * Log: /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-glibc-headers.log
> * Emerging cross-glibc-headers ...
>
> * error: glibc failed :(
> *
> * If you file a bug, please attach the following logfiles:
> * /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-info.log
> * /var/log/portage/cross-mipsr5900el-unknown-linux-gnu-glibc-headers.log.xz
> * /var/tmp/portage/cross-mipsr5900el-unknown-linux-gnu/glibc*/temp/glibc-config.logs.tar.xz
> The command '/bin/sh -c crossdev -s3 -t mipsr5900el-unknown-linux-gnu --binutils ">=2.30" --gcc ">=7.2.0"' returned a non-zero code: 1
I would recommend using GCC 8.2.0, by omitting the --binutils and --gcc
options to crossdev, unless you would like to debug this particular
combination of GCC and Glibc (which I can confirm seems broke). Updated
and much simplified R5900 patches are available in my previous email:
http://lists.nongnu.org/archive/html/qemu-devel/2018-11/msg03649.html
Hopefully soon, with upcoming GCC and Gblic releases, no R5900 patches
are needed at all. Also, a new -mfix-r5900 option has been proposed to
both GAS and GCC:
http://www.sourceware.org/ml/binutils/2018-10/msg00301.html
https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00773.html
With that option one can compile e.g. MIPS II or MIPS III that also
work with the R5900.
The R3900 and the R5900 could for example run the same programs then,
and I do hope that Philippe will be able to merge his R3900 series
eventually.
Fredrik
next prev parent reply other threads:[~2018-11-19 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 20:33 [Qemu-devel] [RFC PATCH 0/2] docker: Add gentoo-mipsr5900el-cross image Philippe Mathieu-Daudé
2018-11-18 20:33 ` [Qemu-devel] [RFC PATCH 1/2] " Philippe Mathieu-Daudé
2018-11-19 10:25 ` Philippe Mathieu-Daudé
2018-11-19 12:23 ` Alex Bennée
2018-11-19 14:11 ` Philippe Mathieu-Daudé
2018-11-19 15:55 ` Fredrik Noring [this message]
2018-11-19 13:44 ` Alex Bennée
2018-11-19 15:34 ` Alex Bennée
2018-11-18 20:33 ` [Qemu-devel] [RFC PATCH 2/2] shippable: Add the mipsr5900el linux-user target Philippe Mathieu-Daudé
2018-11-18 21:03 ` [Qemu-devel] [RFC PATCH 0/2] docker: Add gentoo-mipsr5900el-cross image no-reply
2018-11-19 15:29 ` Fredrik Noring
2018-11-19 15:46 ` Maciej W. Rozycki
2018-11-19 16:27 ` Fredrik Noring
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=20181119155548.GB2405@sx9 \
--to=noring@nocrew.org \
--cc=JuergenUrban@gmx.de \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=macro@linux-mips.org \
--cc=qemu-devel@nongnu.org \
--cc=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).