[Slackbuilds-users] Qemu 7.2.0

[KB_SBo]

On 1/1/23 19:31, Christoph Willing wrote:
> On 2/1/23 13:01, KB_SBo wrote:
>> 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 all
>>>>>
>>>>> FYI
>>>>>
>>>>> *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
>>>>>
>>>>> Cheers
>>>>>
>>>> Hello 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.
>>>>
>>>> -Ed
>>>>
>>>>
>>>>
>>>>
>>> Run-time dependency slirpfound: NO(tried pkgconfig)
>>>
>>> ../meson.build:679:2: ERROR:Dependency "slirp" not found, tried pkgconfig
>>>
>>>
>>>
>> Pretty weird. Doesn't do that here. I'll check again later.
> 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.
>
Indeed. That is part of the definition of a hard dependency: required to
compile and/or run.  Anything else is optional.

>
> ^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.

Not "all".  I rarely use user mode networking. I've updated the README
to provide more details and instruction.

>
> 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.

Either Slackware can add libslirp to the main tree, or if it remains in
SBo, it will be optional like the bunch of other options already listed.
I am loathe to add only libslirp as a hard dependency and ignore the
rest. For example, usbredir is required for USB device pass-through.
There must be someone that uses USB?
>
> 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.
>

https://git.slackbuilds.org/slackbuilds/commit/?id=577581d3e

Life is but a string of surprises. RTFM, FAQs and READMEs.

-Ed