From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12521] RISCV RV32IA selected, RV64GC output
Date: Mon, 03 Feb 2020 09:35:35 +0000 [thread overview]
Message-ID: <bug-12521-163-9hMv3WeLwS@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12521-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12521
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for your report. Instead of looking at the kernel code, could you
instead look at some user-space application or library ?
Indeed, the kernel build system very often overrides the toolchain
architecture/ABI flags, depending on the kernel configuration.
Also, could you share a Buildroot .config file that allows to reproduce the
issue ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-02-03 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 0:18 [Buildroot] [Bug 12521] New: RISCV RV32IA selected, RV64GC output bugzilla at busybox.net
2020-02-03 9:35 ` bugzilla at busybox.net [this message]
2020-02-28 15:58 ` [Buildroot] [Bug 12521] " bugzilla at busybox.net
2020-02-28 16:33 ` bugzilla at busybox.net
2020-03-04 14:10 ` bugzilla at busybox.net
2020-05-18 7:37 ` bugzilla at busybox.net
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=bug-12521-163-9hMv3WeLwS@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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