From: Geert Stappers <stappers@stappers.nl>
To: Andrea Righi <andrea.righi@canonical.com>,
rust-for-linux@vger.kernel.org
Subject: Re: distribute linux-headers to build out-of-tree Rust modules
Date: Sat, 11 Mar 2023 15:51:20 +0100 [thread overview]
Message-ID: <ZAyVaAs/HMLKilkD@gpm.stappers.nl> (raw)
In-Reply-To: <ZAyJnCKa65WKozEJ@righiandr-XPS-13-7390>
On Sat, Mar 11, 2023 at 03:01:00PM +0100, Andrea Righi wrote:
> Hello,
>
> I'm trying to distribute a linux-headers package (deb) that would allow
> to build out-of-tree Rust modules.
>
> Everything looks fine, except for the following error:
>
> error[E0461]: couldn't find crate `core` with expected target triple target-10951614936105594995
Number ends with 4995
> |
> = note: the following crate versions were found:
> crate `core`, target triple target-3759196539525232825: /usr/src/linux-headers-6.2.0-16-generic/rust/libcore.rmeta
Number ends with 2825
> All I need to do is to "refresh" the headers by running a
> "make modules_prepare" after installing my linux-headers package on my
> system and then everything works perfectly.
Acknowledge
> Is this because my system, where I try to build the out-of-tree module,
> has different toolchain versions (e.g., binutils) than the build host?
>
> Any pointer/documentation to better understand how the target triple
> version is determined?
I don't know and I could not resist to ask:
Would it make sense that
make
would include
make modules_prepare
?
Groeten
Geert Stappers
--
Silence is hard to parse
next prev parent reply other threads:[~2023-03-11 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 14:01 distribute linux-headers to build out-of-tree Rust modules Andrea Righi
2023-03-11 14:51 ` Geert Stappers [this message]
2023-03-11 16:27 ` Björn Roy Baron
2023-03-11 20:03 ` Andrea Righi
2023-03-12 13:39 ` Vincenzo Palazzo
2023-03-12 22:08 ` Andrea Righi
2023-03-13 1:35 ` Miguel Ojeda
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=ZAyVaAs/HMLKilkD@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=andrea.righi@canonical.com \
--cc=rust-for-linux@vger.kernel.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