public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] systemd: Allow native build
Date: Thu, 30 Mar 2023 16:51:23 +0200	[thread overview]
Message-ID: <7eb81976-7603-e6c5-264f-19f20724cbc4@gmail.com> (raw)
In-Reply-To: <CANNYZj_RSRs=e5NS4QT=BnyYasf8-PrpFjSkfhPZCPLqtwZ1+w@mail.gmail.com>

2023. 03. 30. 16:41 keltezéssel, Alexander Kanavin írta:
> On Thu, 30 Mar 2023 at 16:31, Böszörményi Zoltán <zboszor@gmail.com> wrote:
>> The mariadb change to use CROSSCOMPILING_EMULATOR
>> instead of building mariadb-native was reverted because
>> qemu is not ominpotent. The same applies to meson
>> running executables via qemu. No custom wrapper would help.
> Mariadb's problem was that (for a specific target) it somehow included
> CPU instructions that qemu usermode doesn't support, and no one looked
> into what those instructions were and why they were produced in the
> first place, preferring to revert the whole thing. There are lots of
> counter-examples in core where qemu usermode works fine, and has been
> working that way for many years, for example gobject introspection, or
> all of the scripts in ../scripts/postinst-intercepts/ which run every
> time you bake an image, including update_udev_hwdb by the way that
> runs target udevadm. I am not maintaining oe-devel, and I do not keep
> an eye on things like that, otherwise I would've asked for further
> investigation into what crashes and why.
>
> I do not want to add complex native dependency chains when usermode
> would work. It's me who's going to fix them when they break, not you.
>
>> You seem to have omitted reading a large part in the
>> commit message for the systemd change.
>>
>>> TODO? The new natively built systemctl binary may replace
>>> the script in systemd-systemctl-native, as it supports
>>> more options and works better than the script. For example,
>>> the current script does not create the symlinks in
>>> /etc/systemd/system for WantedBy= and RequiredBy= settings
>>> and does not support systemctl set-default some.target.
> This is a separate concern, and needs to be proposed as such.

I can extend this patchset to remove systemd-systemctl-native.bb
and use the native build fixing these problems.

Then libfprint can just use that as an innocent bystander.



  reply	other threads:[~2023-03-30 14:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 13:42 [PATCH 1/2] systemd: Allow native build Zoltán Böszörményi
2023-03-30 13:42 ` [PATCH 2/2] libgudev: " Zoltán Böszörményi
2023-03-30 13:47   ` [OE-core] " Alexander Kanavin
2023-03-30 14:01     ` Böszörményi Zoltán
2023-03-30 13:46 ` [OE-core] [PATCH 1/2] systemd: " Alexander Kanavin
2023-03-30 14:04   ` Böszörményi Zoltán
2023-03-30 13:50 ` Richard Purdie
2023-03-30 14:08   ` Böszörményi Zoltán
2023-03-30 14:10     ` Alexander Kanavin
2023-03-30 14:31       ` Böszörményi Zoltán
2023-03-30 14:41         ` Alexander Kanavin
2023-03-30 14:51           ` Böszörményi Zoltán [this message]
2023-03-30 14:57             ` Alexander Kanavin
     [not found]       ` <175138E3E9EE1FF1.27612@lists.openembedded.org>
2023-03-30 14:45         ` Böszörményi Zoltán
2023-03-30 16:39       ` Richard Purdie
2023-03-31  9:39         ` Böszörményi Zoltán
     [not found]         ` <1751778F66ADC2DD.27612@lists.openembedded.org>
2023-03-31  9:46           ` Böszörményi Zoltán
2023-04-03 10:59             ` Ross Burton
2023-04-03 13:00               ` Böszörményi Zoltán
2023-04-03 19:52                 ` Ross Burton
2023-04-04  8:31                   ` Böszörményi Zoltán

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=7eb81976-7603-e6c5-264f-19f20724cbc4@gmail.com \
    --to=zboszor@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox