Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 11 of 45 FirstFirst ... 91011121321 ... LastLast
Results 151 to 165 of 664

Thread: Build my own Vix image

  1. #151

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    Quote Originally Posted by ccs View Post
    Yes - the stick is mounted read-only, the internal hd is mounted as /media/ubuntu/....... and will be why I can save files in the home directory, but not on the stick.

    I'd have thought that the error messages (or lack of) would have indicated that the filesystem was read-only??
    Yes, to stop you changing system files on the stick

  2. #152
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,335
    Thanks
    6,421
    Thanked 9,146 Times in 6,224 Posts
    Quote Originally Posted by lincsat View Post
    ......I'm guessing a depository is offline and I'll try again after the weekend
    That would have given you a fetch error.

  3. #153
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    Quote Originally Posted by ccs View Post
    ... but I fell flat on my face at the first hurdle.
    Full Ubuntu install has got past the first hurdle.

  4. #154

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    Quote Originally Posted by abu baniaz View Post
    That would have given you a fetch error.
    Some of the warnings that flashed through were fetch errors and unable to locate checksum files.

  5. #155
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,335
    Thanks
    6,421
    Thanked 9,146 Times in 6,224 Posts
    you can ignore warnings, errors stop the build.

  6. #156

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    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

    Summary: 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
    For the Vu+ Ultimo4k, it's just the qemu-native that fails

    @CCS have you managed to complete a build or at least do qemu-native

  7. #157
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    ... 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.

  8. #158
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,055
    Thanks
    747
    Thanked 400 Times in 301 Posts
    I've built a release build for the H7 successfully (openvix-5.4.000.release-zgemmah7_usb)

  9. #159

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    I get the same
    Code:
    undefined reference to `stime'
    @ 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.

  10. #160
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    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.

  11. #161
    Willo3092's Avatar
    Title
    ViX Beta Tester
    Join Date
    Oct 2016
    Location
    East Midlands
    Posts
    1,055
    Thanks
    747
    Thanked 400 Times in 301 Posts
    Quote Originally Posted by lincsat View Post
    I get the same
    Code:
    undefined reference to `stime'
    @ Willo3092 was your qemu already compiled?
    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.

  12. #162
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    I'm using Ubuntu 20.04.....

    Man page for stime could have the answer? .....

    Code:
    http://manpages.ubuntu.com/manpages/focal/man2/stime.2.html
    Starting 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.

  13. #163
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by lincsat View Post
    For the Vu+ Ultimo4k, it's just the qemu-native that fails

    @CCS have you managed to complete a build or at least do qemu-native
    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:

    Code:
    https://bugs.launchpad.net/qemu/+bug/1852115
    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.
    Originally Posted by birdman
    It seems that I haven't submitted the patch yet though....I'll have to sort out which repository it is in.
    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?
    But if it were using qemu 4.2 (as it appears it should be?) this wouldn't be an issue.

    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

  14. #164
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    .... they're all restricted access.

  15. #165
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by birdman View Post
    I'll track down my fix....
    In oe-alliance/openembedded-core/meta/recipes-devtools/qemu

    Edit qemu.inc to add:
    Code:
               file://0100-stime-call-gone.patch \
    at the end of the SRC_URI (so after file://CVE-2019-15890.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

  16. The Following 2 Users Say Thank You to birdman For This Useful Post:

    lincsat (01-08-20),Willo3092 (01-08-20)

Page 11 of 45 FirstFirst ... 91011121321 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.