Description
The infamous build error when cross-compiling to QNX on Windows with "g++" not being in the PATH happens significantly more often under the kvm virtualization than under vSphere.
We do know that this is a race-condition somewhere. But unfortunately we don't know what aspect of the system triggers it. In this scenario we are using a different hypervisor (qemu/kvm), different physical hardware and a different storage layer.
This is important to the OpenNebula transition project as this being present will cause a lot more "stage again" type of situations as today.
Attachments
Issue Links
- mentioned in
-
Page Loading...
For Gerrit Dashboard: COIN-85 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
196488,3 | Remove QNX Windows builds | 5.6 | qt/qt5 | Status: MERGED | +2 | 0 |
203488,7 | Provision and build QNX660 on Win 10 x64 | 5.6.3 | qt/qt5 | Status: MERGED | -2 | 0 |
207023,1 | Provision and build QNX660 on Win 10 x64 | 5.9.2 | qt/qt5 | Status: ABANDONED | 0 | 0 |