you can ignore warnings, errors stop the build.
Well whatever I try and after multiple build attempts using the -k (keep going) argument, there are 3 components that don't build for the ZGemma H7
For the Vu+ Ultimo4k, it's just the qemu-native that failsSummary: 3 tasks failed:
/home/openvixbuilder/openvix/build-enviroment/openembedded-core/meta/recipes-devtools/qemu/qemu-native_4.1.0.bb:do_compile
/home/openvixbuilder/openvix/build-enviroment/openembedded-core/meta/recipes-support/boost/boost_1.71.0.bb:do_compile
/home/openvixbuilder/openvix/build-enviroment/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_compile
@CCS have you managed to complete a build or at least do qemu-native
... this is where I'm stuck (about 3 minutes ago)....
Code:| /home/openvixbuilder/openvix/build-enviroment/builds/openvix/release/et10000/tmp/hosttools/ld.bfd: linux-user/syscall.o: in function `do_syscall': | /home/openvixbuilder/openvix/build-enviroment/builds/openvix/release/et10000/tmp/work/x86_64-linux/qemu-native/qemu-native-3.0.0-r0/qemu-3.0.0/linux-user/syscall.c:8526: undefined reference to `stime' | collect2: error: ld returned 1 exit status | make[1]: *** [Makefile:199: qemu-i386] Error 1 | make: *** [Makefile:481: subdir-i386-linux-user] Error 2 | ERROR: oe_runmake failed | WARNING: /home/openvixbuilder/openvix/build-enviroment/builds/openvix/release/et10000/tmp/work/x86_64-linux/qemu-native/qemu-native-3.0.0-r0/temp/run.do_compile.834121:1 exit 1 from 'exit 1' | ERROR: Function failed: do_compile (log file is located at /home/openvixbuilder/openvix/build-enviroment/builds/openvix/release/et10000/tmp/work/x86_64-linux/qemu-native/qemu-native-3.0.0-r0/temp/log.do_compile.834121) ERROR: Task (virtual:native:/home/openvixbuilder/openvix/build-enviroment/openembedded-core/meta/recipes-devtools/qemu/qemu_3.0.0.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 1167 tasks of which 1009 didn't need to be rerun and 1 failed. Summary: 1 task failed: virtual:native:/home/openvixbuilder/openvix/build-enviroment/openembedded-core/meta/recipes-devtools/qemu/qemu_3.0.0.bb:do_compile Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. make: *** [Makefile:1029: image] Error 1
Different qemu_3.0.0 to your's. ET10000
tmp/work/x86_64-linux/qemu-native/qemu-native-3.0.0-r0/qemu-3.0.0/linux-user/syscall.c:8526: undefined reference to `stime'
Code:Selecting previously unselected package qemu. Preparing to unpack .../152-qemu_1%3a4.2-3ubuntu6.3_amd64.deb ... Unpacking qemu (1:4.2-3ubuntu6.3) ... Setting up libpcrecpp0v5:amd64 (2:8.39-12build1) ... Setting up qemu (1:4.2-3ubuntu6.3) ... Setting up libglib2.0-dev-bin (2.64.3-1~ubuntu20.04.1) ...
Last edited by ccs; 01-08-20 at 14:53.
I've built a release build for the H7 successfully (openvix-5.4.000.release-zgemmah7_usb)
I get the same@ Willo3092 was your qemu already compiled? I managed to complete a build for the Ultimo4k a few Days ago but since doing a clean Ubuntu install and redownloading the build environment, I can't get that compiled for any image. I'm now wondering if a recent update broke that.Code:undefined reference to `stime'
Maybe related......
Glibc 2.31 porting notes/stime removal
From the release notes:
* The obsolete function stime is no longer available to newly linked
binaries, and its declaration has been removed from <time.h>.
Programs that set the system time should use clock_settime instead.
Also note something which you may want to fix while in the area:
* We plan to remove the obsolete function ftime, and the header
<sys/timeb.h>, in a future version of glibc. In this release, the
header still exists but calling ftime will cause a compiler warning.
All programs should use gettimeofday or clock_gettime instead.
Sorry, I have no idea what that means. I'm very much a bumbling poke and hope merchant
If a build fails, I try a build for something else similar. If that works, 9 times out of 10 the one that failed will now work.
I retired from work yesterday so I promise to try and learn about the stuff I'm dabbling with.
I'm using Ubuntu 20.04.....
Man page for stime could have the answer? .....
Code:http://manpages.ubuntu.com/manpages/focal/man2/stime.2.htmlStarting with glibc 2.31, this function is no longer available to newly linked
applications and is no longer declared in <time.h>.
Last edited by ccs; 01-08-20 at 16:04.
Hmmmm...there was a bug there. I may have applied a patch to my build. I reported it here...
Posts are (restricted links removed, replaced with actual text):
The build fails because of this known bug in qemu:
Anyone with qemu already built may be OK - at least as far as compiling goes - but the qemu version needs to be bumped to fix this.Code:https://bugs.launchpad.net/qemu/+bug/1852115But if it were using qemu 4.2 (as it appears it should be?) this wouldn't be an issue.It seems that I haven't submitted the patch yet though....I'll have to sort out which repository it is in.Originally Posted by birdman
It's in openembedded-core.
However, when I go to that on github I find that master there is configured for qemu 4.2 (which probably has the fix in already). But my fresh download of build-environment 4.4 ends up using qemu 4.1.
Any ideas as to why?
I'll track down my fix....
Last edited by birdman; 01-08-20 at 17:53.
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
.... they're all restricted access.
In oe-alliance/openembedded-core/meta/recipes-devtools/qemu
Edit qemu.inc to add:
at the end of the SRC_URI (so after file://CVE-2019-15890.patch).Code:file://0100-stime-call-gone.patch \
Add this file (unzipped) into the qemu sub-directory as 0100-stime-call-gone.patch
patch.zip
MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD