From: Sumera Priyadarsini <sylphrenadin@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: Build system can't detect rustc
Date: Wed, 17 Mar 2021 16:02:18 +0530 [thread overview]
Message-ID: <CACAkLuopZwyXSMX0TNK_AV=nSjSp7++mXJ7PNeg2_j1bNxrekQ@mail.gmail.com> (raw)
In-Reply-To: <CANiq72=2FJQ7Ct_77MsaYe-3qThuRJ-gkLFvY-acq_GmhR9A4A@mail.gmail.com>
On Tue, Mar 16, 2021 at 8:39 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Tue, Mar 16, 2021 at 3:10 PM Sumera Priyadarsini
> <sylphrenadin@gmail.com> wrote:
> >
> > Hi Miguel,
> >
> > This definitely helped- I was using the master branch earlier. Can I
> > make a PR to add this to the documentation on rust/quick-start page?
>
> I didn't put it there since, if we manage to get this mainlined, then
> we would be in the master branch already. :-)
>
> However, you can send the PR to add a line to the `README.md` file,
> which is only intended for GitHub!
>
> > gcc versions 8 /9 / 10 but the error persists. I am not sure how to
> > proceed here :/
>
> This happens when bindgen (which uses Clang internally) gets GCC
> parameters, but that should not happen and is a bug when it does.
> Which kernel config are you using? defconfig for x86_64?
Hi,
Specifying clang did work, thanks! I used "make nconfig" but I am
guessing it would be the same as what 'defconfig' would have given.
Here is a paste if you want to take a look:
https://paste.ubuntu.com/p/dMb3bb34Qf/
>
> To progress, please try a Clang build (pass CC=clang or LLVM=1 to
> make), which is much more likely to work (GCC builds rely on a hack to
> make bindgen work), or use one of the kernel configs inside
> .github/workflows/ which are known to build since we check them in the
> CI.
>
> HTH,
>
Thanks,
Sumera
> Cheers,
> Miguel
next prev parent reply other threads:[~2021-03-17 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 6:30 Build system can't detect rustc Sumera Priyadarsini
2021-03-15 7:27 ` Geert Stappers
2021-03-15 12:45 ` Miguel Ojeda
2021-03-16 14:10 ` Sumera Priyadarsini
2021-03-16 15:09 ` Miguel Ojeda
2021-03-16 17:00 ` Kaviraj Kanagaraj
2021-03-16 17:31 ` Miguel Ojeda
2021-03-17 10:32 ` Sumera Priyadarsini [this message]
2021-03-17 13:40 ` Miguel Ojeda
2021-03-17 18:04 ` Sumera Priyadarsini
2021-03-17 15:55 ` Miguel Ojeda
2021-03-17 22:49 ` 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='CACAkLuopZwyXSMX0TNK_AV=nSjSp7++mXJ7PNeg2_j1bNxrekQ@mail.gmail.com' \
--to=sylphrenadin@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.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;
as well as URLs for NNTP newsgroup(s).