On Friday 17 October 2014 09.01:07 Jeroen Groenewegen van der Weyden wrote: > Hi, > > Compiling it myself was easier said then done, anybody any idea? > > When I try to compile src package from qemu-1.6.0-4.2.1.src.rpm > > rpmbuild -bb qemu.spec > lot of output and then: > > Processing files: qemu-tools-1.6.0-4.2.1.x86_64 > Provides: config(qemu-tools) = 1.6.0-4.2.1 qemu-tools = 1.6.0-4.2.1 > qemu-tools(x86-64) = 1.6.0-4.2.1 qemu:/usr/lib/qemu-bridge-helper > Requires(interp): /bin/sh /bin/sh > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 > rpmlib(PayloadFilesHavePrefix) <= 4.0-1 > Requires(verify): /bin/sh > Requires(pre): permissions > Requires(post): /bin/sh > Requires(preun): permissions > Requires: libaio.so.1()(64bit) libaio.so.1(LIBAIO_0.1)(64bit) > libaio.so.1(LIBAIO_0.4)(64bit) libc.so.6()(64bit) > libc.so.6(GLIBC_2.10)(64bit) libc.so.6(GLIBC_2.14)(64bit) > libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3)(64bit) > libc.so.6(GLIBC_2.3.2)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) > libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.6)(64bit) > libc.so.6(GLIBC_2.7)(64bit) libc.so.6(GLIBC_2.9)(64bit) > libcap-ng.so.0()(64bit) libcap.so.2()(64bit) libcurl.so.4()(64bit) > libglib-2.0.so.0()(64bit) libgthread-2.0.so.0()(64bit) > libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) > libpthread.so.0(GLIBC_2.3.2)(64bit) librt.so.1()(64bit) > librt.so.1(GLIBC_2.2.5)(64bit) librt.so.1(GLIBC_2.3.3)(64bit) > libuuid.so.1()(64bit) libuuid.so.1(UUID_1.0)(64bit) > libvdeplug.so.3()(64bit) libz.so.1()(64bit) > Processing files: qemu-guest-agent-1.6.0-4.2.1.x86_64 > Provides: qemu-guest-agent = 1.6.0-4.2.1 qemu-guest-agent(x86-64) = > 1.6.0-4.2.1 qemu:/usr/bin/qemu-ga > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 > rpmlib(PayloadFilesHavePrefix) <= 4.0-1 > Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.10)(64bit) > libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) > libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) > libc.so.6(GLIBC_2.4)(64bit) libc.so.6(GLIBC_2.6)(64bit) > libc.so.6(GLIBC_2.7)(64bit) libc.so.6(GLIBC_2.9)(64bit) > libglib-2.0.so.0()(64bit) libgthread-2.0.so.0()(64bit) > libpthread.so.0()(64bit) libpthread.so.0(GLIBC_2.2.5)(64bit) > librt.so.1()(64bit) > Checking for unpackaged file(s): /usr/lib/rpm/check-files > /usr/src/packages/BUILDROOT/qemu-1.6.0-4.2.1.x86_64 > error: Installed (but unpackaged) file(s) found: > /usr/bin/vscclient > /usr/include/cacard/cac.h > /usr/include/cacard/card_7816.h > /usr/include/cacard/card_7816t.h > /usr/include/cacard/eventt.h > /usr/include/cacard/vcard.h > /usr/include/cacard/vcard_emul.h > /usr/include/cacard/vcard_emul_type.h > /usr/include/cacard/vcardt.h > /usr/include/cacard/vcardt_internal.h > /usr/include/cacard/vevent.h > /usr/include/cacard/vreader.h > /usr/include/cacard/vreadert.h > /usr/include/cacard/vscard_common.h > /usr/lib/libcacard.a > /usr/lib/libcacard.la > /usr/lib/libcacard.so > /usr/lib/libcacard.so.0 > /usr/lib/libcacard.so.0.0.0 > /usr/lib/pkgconfig/libcacard.pc > > > RPM build errors: > Installed (but unpackaged) file(s) found: > /usr/bin/vscclient > /usr/include/cacard/cac.h > /usr/include/cacard/card_7816.h > /usr/include/cacard/card_7816t.h > /usr/include/cacard/eventt.h > /usr/include/cacard/vcard.h > /usr/include/cacard/vcard_emul.h > /usr/include/cacard/vcard_emul_type.h > /usr/include/cacard/vcardt.h > /usr/include/cacard/vcardt_internal.h > /usr/include/cacard/vevent.h > /usr/include/cacard/vreader.h > /usr/include/cacard/vreadert.h > /usr/include/cacard/vscard_common.h > /usr/lib/libcacard.a > /usr/lib/libcacard.la > /usr/lib/libcacard.so > /usr/lib/libcacard.so.0 > /usr/lib/libcacard.so.0.0.0 > /usr/lib/pkgconfig/libcacard.pc > > > second try: > > /repositories/home:/olh:/xen-unstable/openSUSE_Factory/src > When I try to compile src package from > qemu-2.1.0-260.xen_unstable.17.src.rpm > > rpmbuild -bb qemu.spec > lot of output and then: > > > Compiling IASL > /usr/src/packages/BUILD/qemu-2.1.0/roms/seabios/builds/seabios-128k/src/fw/acpi-dsdt.hex > ASL Input: > /usr/src/packages/BUILD/qemu-2.1.0/roms/seabios/builds/seabios-128k/src/fw/acpi-dsdt.dsl.i > > - 474 lines, 19153 bytes, 315 keywords > AML Output: /usr/src/packages/BUILD/qemu-2.1.aml - 4405 bytes, 159 > named objects, 156 executable opcodes > Listing File: /usr/src/packages/BUILD/qemu-2.1.lst - 174123 bytes > Hex Dump: /usr/src/packages/BUILD/qemu-2.1.hex - 41680 bytes > > Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 245 Optimizations > Traceback (most recent call last): > File "./scripts/acpi_extract.py", line 237, in <module> > for line in fileinput.input(): > File "/usr/lib64/python2.7/fileinput.py", line 252, in next > line = self.readline() > File "/usr/lib64/python2.7/fileinput.py", line 344, in readline > self._file = open(self._filename, self._mode) > IOError: [Errno 2] No such file or directory: > '/usr/src/packages/BUILD/qemu-2.1.0/roms/seabios/builds/seabios-128k/src/fw/acpi-dsdt.lst' > make[1]: *** > [/usr/src/packages/BUILD/qemu-2.1.0/roms/seabios/builds/seabios-128k/src/fw/acpi-dsdt.hex] > > Error 1 > make[1]: Leaving directory `/usr/src/packages/BUILD/qemu-2.1.0/roms/seabios' > make: *** [build-seabios-config-seabios-128k] Error 2 > make: Leaving directory `/usr/src/packages/BUILD/qemu-2.1.0/roms' > error: Bad exit status from /var/tmp/rpm-tmp.YrxmMQ (%build) > > > RPM build errors: > Bad exit status from /var/tmp/rpm-tmp.YrxmMQ (%build) > > > Jeroen Groenewegen van der Weyden schreef op 16-10-2014 om 12:01: > > Hi, > > > > I am playing around with ceph and at some point the documentation > > states I need a qemu-img version with rbd enabled. > > > > The qemu /qemu-tools versions installed from the standard repositories > > are all without rbd support. > > eg: > > http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/ > > > > Before I start compiling myself, > > 1) Does anybody know about qemu packages with rbd enabled, ready to use > > 2) Why are the standard opensuse qemu packages not compiled with rbd > > enabled? > > > > BR, > > Jeroen > >
I still think it would be easier for you and people wanting to help to simply branch the project on obs in your home. then make your tries there. At the end if they are good, a simple sr will fixe the branched repo and will be available for all. For build error then you can paste the url build log, and people will be able to check your whole project. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
