Yes,  libvirt can be compiled ok and each sub packages are created, for example:

-rw-r--r-- 1 hbai 751     7784 11月 30 22:41 libvirt-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751  1921432 11月 30 22:41 libvirt-docs-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751     8740 11月 30 22:41 libvirt-daemon-config-network-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   700736 11月 30 22:41 libvirt-daemon-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    12728 11月 30 22:41 libvirt-daemon-config-nwfilter-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   243360 11月 30 22:41 libvirt-daemon-driver-network-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    74268 11月 30 22:41 libvirt-daemon-driver-nwfilter-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    48976 11月 30 22:41 libvirt-daemon-driver-nodedev-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    49204 11月 30 22:41 libvirt-daemon-driver-interface-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    37812 11月 30 22:41 libvirt-daemon-driver-secret-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   269600 11月 30 22:41 libvirt-daemon-driver-storage-core-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    40708 11月 30 22:41 libvirt-daemon-driver-storage-logical-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    39512 11月 30 22:41 libvirt-daemon-driver-storage-disk-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    36836 11月 30 22:41 libvirt-daemon-driver-storage-scsi-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    36780 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    38952 11月 30 22:41 libvirt-daemon-driver-storage-iscsi-direct-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    35020 11月 30 22:41 libvirt-daemon-driver-storage-mpath-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    48772 11月 30 22:41 libvirt-daemon-driver-storage-gluster-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751    43076 11月 30 22:41 libvirt-daemon-driver-storage-rbd-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751     6756 11月 30 22:41 libvirt-daemon-driver-storage-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751   612932 11月 30 22:41 libvirt-daemon-driver-qemu-4.7.0-1.tis.101.x86_64.rpm

-rw-r--r-- 1 hbai 751     6540 11月 30 22:41 libvirt-daemon-lxc-4.7.0-1.tis.101.x86_64.rpm

……

But “build-iso”  complains:

10:19:34 Could not resolve packages:  libvirt libvirt-client libvirt-daemon libvirt-daemon-config-network

It seems version conflicts with “libvirt.so”  and some “python2” upgrading to “python3” runtime dependency issues have not been resolved yet.

From: fuyong <fuyong@neusoft.com>
Sent: Tuesday, December 1, 2020 9:12 AM
To: Bai, Haiqing <Haiqing.Bai@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] [Centos8] build-iso runtime dependency issue

[Please note this e-mail is from an EXTERNAL e-mail address]

Hi Haiqing Bai

Has libvirt compiled successfully in your integ directory?
python3-ipaddr has no el8 version.

At present, you need to comment out the place where python3-ipaddr is dependent

B,R

Yong 

On 2020/11/30 上午10:26, Bai, Haiqing wrote:

Build-iso on f/centos8 branch has below runtime dependency list:

==============================================================

Warning: Infinite loop detected in dependency resolution.  See /localdisk/loadbuild/hbai/c81nststx/export/deps.txt for details -- exiting

These RPMS had problems (likely version conflicts)

        libvirt-daemon

        libvirt-daemon-driver-network

        libvirt.so.0()(64bit)

        libvirt.so.0(LIBVIRT_0.0.3)(64bit)

        libvirt.so.0(LIBVIRT_0.1.0)(64bit)

        libvirt.so.0(LIBVIRT_0.6.1)(64bit)

        libvirt.so.0(LIBVIRT_0.9.0)(64bit)

        libvirt.so.0(LIBVIRT_0.9.3)(64bit)

        libvirt.so.0(LIBVIRT_1.0.2)(64bit)

        libvirt.so.0(LIBVIRT_1.0.6)(64bit)

        libvirt.so.0(LIBVIRT_4.5.0)(64bit)

        libvirt.so.0(LIBVIRT_PRIVATE_4.7.0)(64bit)

        python3-ipaddr

        python3-ipaddress

        python-kubernetes

        python-pint

        PyYAML

        qemu-kvm-ev

I remembered the python3-ipaddr issue had been mentioned before by some guys,  anyone knows the latest status of that issue?  thanks

B,R

Haiqing Bai 

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication
is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------