On 2/1/23 13:01, KB_SBo wrote:
I can confirm that qemu builds fine without libslirp being present. The search for libslirp during configuration merely determines whether user mode networking is compiled in - failure to find libslirp is not critical to compiling an executable.On 1/1/23 18:06, marav wrote:Le 02/01/2023 à 02:49, KB_SBo a écrit :On 12/16/22 13:11, marav wrote:Hi Edward, hi allFYI *libslirp *is now required as an additional dependency to compile qemu 7.2.0 https://wiki.qemu.org/ChangeLog/7.2#Removal_of_the_.22slirp.22_submodule_.28affects_.22-netdev_user.22.29 CheersHello All, Actually not true. libslirp is NOT a compile dependency, but optional for user mode networking. Qemu compiles just fine without it. From Qemu ChangeLog/7.2 The "slirp" submodule / code (which is the code behind "-netdev user" / "-nic user") has been removed from the QEMU source tree, so you now need to install your distributions libslirp development package before compiling QEMU to get the user-mode networking feature included again. Since Slackware does not have a "distribution package" (SBo provides this functionality), libslirp is technically OPTIONAL. I should have been a bit more clear in the README and forgot to add the --enable-slirp option as a switch. -EdRun-time dependency slirpfound: NO(tried pkgconfig) ../meson.build:679:2: ERROR:Dependency "slirp" not found, tried pkgconfigPretty weird. Doesn't do that here. I'll check again later.
However the loss of user mode networking in the resulting qemu executable breaks the longstanding "principle of least surprise" which includes:
The principle of least astonishment (POLA), aka principle of least surprise (alternatively a law or rule),[1][2] applies to user interface and software design.[3] It proposes that a component of a system should behave in a way that most users will expect it to behave. The behavior should not astonish or surprise users. The following is a formal statement of the principle: "If a necessary feature has a high astonishment factor, it may be necessary to redesign the feature."[4]Since we have all enjoyed built-in user mode networking in qemu for as long as I've been using it (long time), it's disappearance after the last update was definitely a surprise (although it is mentioned in the README). It seems others have also been surprised.
I understand that maintainers don't want to enable all possible features in their SlackBuilds. However I personally don't believe that SlackBuilds should be configured in the most minimalistic manner either. Slackware itself is not a minimalistic distribution; its packages offer the most useful features (by someone's opinion), not the minimum features needed to produce a package.
I think a feature so basic as user mode networking should be included by default; adding libslirp as a hard dependency would enable it and avoid the surprise of its absence.
chris
_______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
