Re: [Development] CI upgrade
On Thursday, 3 January 2019 08:10:14 -02 Tony Sarajärvi wrote: > openNebula uses QEMU that uses libvirt to create a VM using KVM: Despite the name, in this mode QEMU is not emulating anything. When assisted by KVM this is real hardware virtualisation and qemu only serves to provide the virtual HW. This is called "qemu system" because it emulates the entire system and runs a full OS. That's very different from "qemu user" which we use to test the ARM builds on a regular x86 Linux host. That one does not emulate the whole system, just the CPU and it translates system calls from one ABI to the other. This mode is far buggier since the system call translation layer is very incomplete. So my answer stands: I don't see how qemu could be involved. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] CI upgrade
>On Wednesday, 2 January 2019 04:34:43 -02 Tony Sarajärvi wrote: >> agent:2019/01/01 20:15:26 build.go:193: Config: Using QtTest library >> 5.12.0, Qt 5.12.0 (x86_64-little_endian-lp64 shared (dynamic) release >> build; by GCC >> 5.3.1 20160406 (Red Hat 5.3.1-6)) >This is a native x86-64 build and run. I don't see how it could be related to >QEMU. >The other one you said is Windows 10, so I don't see how it would be QEMU >either. openNebula uses QEMU that uses libvirt to create a VM using KVM: root@calm-squid:/var/log/libvirt/qemu# cat one-2474429.log 2018-12-31 06:28:04.959+: starting up libvirt version: 3.6.0, package: 1ubuntu6.8 (Marc Deslauriers Wed, 23 May 2018 13:23:59 -0400), qemu version: 2.10.1(Debian 1:2.10+dfsg-0ubuntu3.8), hostname: calm-squid LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name guest=one-2474429,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-8102-one-2474429/master-key.aes -machine pc-i440fx-artful,accel=kvm,usb=off,dump-guest-core=off -cpu qemu64,ssse3=on,svm=off,vmx=off -m 6144 -realtime mlock=off -smp 2,sockets=1,cores=2,threads=1 -uuid edb33d53-187d-4448-9835-54c303297131 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-8102-one-2474429/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device ahci,id=sata0,bus=pci.0,addr=0x4 -drive file=/var/lib/one//datastores/0/2474429/disk.0,format=qcow2,if=none,id=drive-sata0-0-0,cache=unsafe -device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/var/lib/one//datastores/0/2474429/disk.1,format=raw,if=none,media=cdrom,id=drive-sata0-0-1,readonly=on -device ide-cd,bus=sata0.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev tap,fd=31,id=hostnet0,vhost=on,vhostfd=33 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=02:06:d3:d3:d0:ee,bus=pci.0,addr=0x3 -vnc 0.0.0.0:29394 -device VGA,id=video0,vgamem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on 2018-12-31T06:29:41.783344Z qemu-system-x86_64: terminating on signal 15 from pid 6092 (/usr/sbin/libvirtd) 2018-12-31 06:29:43.984+: shutting down, reason=destroyed ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] should 5.12 build on iOS ?
> On 28 Dec 2018, at 17:19, Martin Koller wrote: > > A colleague built 5.12 for iOS but got linker errors: > > Undefined symbols for architecture arm64: > "_CGImageDestinationCreateWithData", referenced from: > QMacPasteboardMimeTiff::convertFromMime(QString const&, QVariant, > QString) in libQt5ClipboardSupport.a(qmacmime.o) > "_CGImageDestinationAddImage", referenced from: > QMacPasteboardMimeTiff::convertFromMime(QString const&, QVariant, > QString) in libQt5ClipboardSupport.a(qmacmime.o) > "_CGImageDestinationFinalize", referenced from: > QMacPasteboardMimeTiff::convertFromMime(QString const&, QVariant, > QString) in libQt5ClipboardSupport.a(qmacmime.o) > "_CGImageSourceCreateWithData", referenced from: > QMacPasteboardMimeTiff::convertToMime(QString const&, QList, > QString) in libQt5ClipboardSupport.a(qmacmime.o) > "_kCGImagePropertyPixelWidth", referenced from: > QMacPasteboardMimeTiff::convertFromMime(QString const&, QVariant, > QString) in libQt5ClipboardSupport.a(qmacmime.o) > "_kCGImagePropertyPixelHeight", referenced from: > QMacPasteboardMimeTiff::convertFromMime(QString const&, QVariant, > QString) in libQt5ClipboardSupport.a(qmacmime.o) > "_CGImageSourceCreateImageAtIndex", referenced from: > QMacPasteboardMimeTiff::convertToMime(QString const&, QList, > QString) in libQt5ClipboardSupport.a(qmacmime.o) > ld: symbol(s) not found for architecture arm64 > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > > He says it's due to the Cocoa Framework no existing on iOS > > is this known or a problem with our local build ? Hi, This *should* work, since the CGImage functions lives in the ImageIO framework, which is available on both iOS and macOS, and is included by qtbase/src/platformsupport/clipboard/clipboard.pro, I have not tried a 5.12 iOS build myself though. Morten ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt 5.12 branch is broken for Android
Hi, [...] > > Now configure mixes host libs with the target (android) ones, which IMHO > > is > > very wrong when cross-compiling :). > > Can some qmake master take a look and fix the problem? > > if you're sure you have the latest revision and a completely clean build > tree (including no stray .qmake.cache/.stash/.super files there or > up-tree), make a _proper_ bug report on jira and make sure it's assigned > to me. > that applies to any _recent_ regressions introduced by me. Done https://bugreports.qt.io/browse/QTBUG-72834 , though I have no idea if any of your patches caused this problem. I'm not blaming anyone for this problems, I'm just crying for help :). Cheers, BogDan. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
