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: Tue, 16 Mar 2021 19:40:28 +0530 [thread overview]
Message-ID: <CACAkLuqMrRAE6d8dP_b9khtO3HY4mnEGP_Z+1HhzRYDMOaaN+Q@mail.gmail.com> (raw)
In-Reply-To: <CANiq72=ZUr5JcfnMYB_=Gnsi08q45PwOUo3-CPL84_d5G2EV1w@mail.gmail.com>
On Mon, Mar 15, 2021 at 6:16 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> Hi Sumera,
>
> On Mon, Mar 15, 2021 at 7:30 AM Sumera Priyadarsini
> <sylphrenadin@gmail.com> wrote:
> >
> > Could you point me to where make is trying to find rust or how I can try
> > fixing this? Is there anything else I might have missed out on?
> > I have the latest rust nightly installed.
>
> By default, it will call `rustc` as-is, so make sure it is on your $PATH:
>
> $ which rustc
> /some/path/bin/rustc
>
> Another reason could be that you are using the `master` branch instead
> of the `rust` branch.
>
> HTH,
>
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 did run into some other errors while building though:
```
error: unknown argument: '-mindirect-branch=thunk-extern', err: true
error: unknown argument: '-mindirect-branch-register', err: true
error: unsupported option '-mrecord-mcount' for target
'x86_64-pc-linux-gnu', err: true
thread 'main' panicked at 'Unable to generate bindings: ()'
```
The full logs are here: https://paste.ubuntu.com/p/xqd4pMBdrb/
Since a few places online suggested the error might be related to gcc
and clang, I tried compiling with clang versions 9.0 /10.0 /11.0 and
gcc versions 8 /9 / 10 but the error persists. I am not sure how to
proceed here :/
Thanks,
Sumera
> Cheers,
> Miguel
next prev parent reply other threads:[~2021-03-16 14:11 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 [this message]
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
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=CACAkLuqMrRAE6d8dP_b9khtO3HY4mnEGP_Z+1HhzRYDMOaaN+Q@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).