From: Markus Volk <f_l_k@t-online.de>
To: ChenQi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][oe-core][PATCH] systemd: dont allow autoselect for meson
Date: Mon, 11 Nov 2024 10:48:25 +0100 [thread overview]
Message-ID: <PW5SMS.YER64B7Q8HYQ@t-online.de> (raw)
In-Reply-To: <02ea8fa9-b33d-4f10-b8a9-98a4f62c1d1f@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Mon, Nov 11 2024 at 03:07:30 PM +08:00:00, ChenQi
<Qi.Chen@windriver.com> wrote:
> ?
1) I didn't diff the output files yet, so I don't have a valid answer
to this. I just looked at log.do_configure with and without this option
and did some runtime testing
2) Generally speaking, a binary changes when a feature is added.
Ideally, a feature should only be added if this is explicitly
specified. Otherwise there can always be differences (e.g. because a
tool is searched for and found on the host machine). This can lead to
different results on different distributions/installations.
[-- Attachment #2: Type: text/html, Size: 765 bytes --]
next prev parent reply other threads:[~2024-11-11 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 13:28 [RFC][oe-core][PATCH] systemd: dont allow autoselect for meson Markus Volk
2024-11-10 14:40 ` Alexander Kanavin
2024-11-10 14:52 ` Markus Volk
[not found] ` <1806A2E5B9CEF1AC.19665@lists.openembedded.org>
2024-11-10 15:23 ` Markus Volk
2024-11-10 16:33 ` Alexander Kanavin
2024-11-10 16:43 ` Markus Volk
2024-11-11 11:03 ` Alexander Kanavin
2024-11-11 13:31 ` Ross Burton
2024-11-12 6:51 ` Markus Volk
2024-11-11 7:07 ` ChenQi
2024-11-11 9:48 ` Markus Volk [this message]
2024-11-11 10:49 ` Alexander Kanavin
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=PW5SMS.YER64B7Q8HYQ@t-online.de \
--to=f_l_k@t-online.de \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.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.