From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] rust: why is it built in do_install()
Date: Sat, 02 Sep 2023 11:22:43 +0200 [thread overview]
Message-ID: <lypm31exp8.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CANNYZj8jxOoj0sta7rp5EZdBqR=HX6hs45e6Co5znRzBLkyrRQ@mail.gmail.com> (Alexander Kanavin's message of "Sat, 2 Sep 2023 07:09:06 +0200")
Alexander Kanavin <alex.kanavin@gmail.com> writes:
> Any changes would have to fulfil this:
>
> 1. Rust's installation procedure should run under pseudo, e.g. in
> do_install.
The current recipe does *not* run installation under pseudo
| rust_do_install:class-target() {
| export PSEUDO_UNLOAD=1
| rust_runx install
Only class-native runs under pseudo (or is pseudo automatically disabled
for this class?).
Enrico
next prev parent reply other threads:[~2023-09-02 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 16:34 rust: why is it built in do_install() Enrico Scholz
2023-09-01 17:37 ` [OE-core] " Frédéric Martinsons
2023-09-01 21:22 ` Richard Purdie
2023-09-02 5:09 ` Alexander Kanavin
2023-09-02 9:22 ` Enrico Scholz [this message]
2023-09-02 9:49 ` Richard Purdie
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=lypm31exp8.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.