From: Neal Gompa <ngompa@fedoraproject.org>
To: rust-for-linux@vger.kernel.org
Cc: Miguel Ojeda <ojeda@kernel.org>, Quentin Monnet <qmo@kernel.org>,
bpf@vger.kernel.org,
"Justin M. Forbes" <jforbes@fedoraproject.org>,
Davide Cavalca <dcavalca@fedoraproject.org>,
Janne Grunau <jannau@fedoraproject.org>,
Hector Martin <marcan@fedoraproject.org>,
Asahi Linux <asahi@lists.linux.dev>
Subject: Weird failure with bpftool when building 6.11-rc4 with clang+rust+lto
Date: Tue, 20 Aug 2024 08:02:01 -0400 [thread overview]
Message-ID: <CAEg-Je8=t_cXKsWL0XSx3vF1gsArSWpychfbEf+yjM6wVz3Mjw@mail.gmail.com> (raw)
Hey all,
While working on enabling Rust in the Fedora kernel[1], we've managed
to get the setup almost completely working, but we have a build
failure with the clang+lto build variant[2][3].
Based on the build failure log[4][5], it looks like there's some
random mixing of Rust inside of C code or something of the sort (which
obviously would be invalid).
Can someone help with this?
Thanks in advance and best regards,
[1]: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3295
[2]: https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/index.html?prefix=trusted-artifacts/1419488480/build_x86_64/7618803903/artifacts/
[3]: https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/index.html?prefix=trusted-artifacts/1419488480/build_aarch64/7618803917/artifacts/
[4]: https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1419488480/build_x86_64/7618803903/artifacts/build-failure.log
[5]: https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/1419488480/build_aarch64/7618803917/artifacts/build-failure.log
--
Neal Gompa (FAS: ngompa)
next reply other threads:[~2024-08-20 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 12:02 Neal Gompa [this message]
2024-08-20 16:48 ` Weird failure with bpftool when building 6.11-rc4 with clang+rust+lto Matthew Maurer
2024-08-23 21:45 ` Neal Gompa
2024-08-31 11:25 ` Neal Gompa
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='CAEg-Je8=t_cXKsWL0XSx3vF1gsArSWpychfbEf+yjM6wVz3Mjw@mail.gmail.com' \
--to=ngompa@fedoraproject.org \
--cc=asahi@lists.linux.dev \
--cc=bpf@vger.kernel.org \
--cc=dcavalca@fedoraproject.org \
--cc=jannau@fedoraproject.org \
--cc=jforbes@fedoraproject.org \
--cc=marcan@fedoraproject.org \
--cc=ojeda@kernel.org \
--cc=qmo@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).