rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Hindborg (Samsung)" <nmi@metaspace.dk>
To: Philipp Stanner <pstanner@redhat.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: RfL currently does not integrate very well with some Kconfigs
Date: Fri, 16 Feb 2024 20:25:26 +0100	[thread overview]
Message-ID: <87cyswp5ra.fsf@metaspace.dk> (raw)
In-Reply-To: <803d666dcd5b1f927590719c10bdd90ce2ba6dd0.camel@redhat.com>


Philipp Stanner <pstanner@redhat.com> writes:


<snip>

>
> Strong suspect for the cause is that this function is defined as part
> of MSI, so just activating PCI doesn't suffice.
>
> I verified that this is indeed a config problem. The entire toolchain
> is installed according to the official documentation, selecting that
> one compiler version that currently works etc.
>
> Setting PCI + MSI (and, in Hacking, Rust Hacking -> Allow unoptimized
> build-time assertations) results in a valid build.
>
>
> So, it would seem there are some "deponds on" entries missing
> somewhere.
> Is this problem known? Any plans or suggestions how to deal with it?
>
> My instinct tells me that there could be many potentially broken
> configs out there.

Thanks for reporting. I think it is fixed now.

BR Andreas


      parent reply	other threads:[~2024-02-16 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 15:21 RfL currently does not integrate very well with some Kconfigs Philipp Stanner
2024-02-15 16:22 ` Miguel Ojeda
2024-02-15 17:29   ` Andreas Hindborg (Samsung)
2024-02-16 19:25 ` Andreas Hindborg (Samsung) [this message]

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=87cyswp5ra.fsf@metaspace.dk \
    --to=nmi@metaspace.dk \
    --cc=pstanner@redhat.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).