Re: [yocto] yocto jethro failed on gettext-native
Hello Paul, Could you, please, read couple of times more my quoted comment (by you)? Stress to word: *couple*! ;-) > Now, I must admit, I have learned something new. Never gave any > consideration to these releases: example: Pyro 17.0.3. > >* But now I understand: it has direct link with Ubuntu 17... Even, YOCTO* > *Pyro, as given example, can be substituted with Ubuntu 17.04?! Wow... * Thank you, Zoran ___ On Wed, May 2, 2018 at 10:36 PM, Paul Barker wrote: > On Wed, 25 Apr 2018, at 21:55, Zoran Stojsavljevic wrote: > > > Jethro doesn't support Yocto 16.* because it is very old (released > 2015...)... > > > > Now, I must admit, I have learned something new. Never gave any > > consideration to these releases: example: Pyro 17.0.3. > > > > But now I understand: it has direct link with Ubuntu 17... Even, YOCTO > > Pyro, as given example, can be substituted with Ubuntu 17.04?! Wow... > > > > Every day in every way, I'm progressing more and more! ;-) > > > > You seem to be a bit confused here by the fact that the poky version > number lined up with the year in 2017. See https://wiki.yoctoproject.org/ > wiki/Releases for some context. > > -- > Paul Barker > Beta Five Ltd > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On Wed, 25 Apr 2018, at 21:55, Zoran Stojsavljevic wrote: > > Jethro doesn't support Yocto 16.* because it is very old (released > > 2015...)... > > Now, I must admit, I have learned something new. Never gave any > consideration to these releases: example: Pyro 17.0.3. > > But now I understand: it has direct link with Ubuntu 17... Even, YOCTO > Pyro, as given example, can be substituted with Ubuntu 17.04?! Wow... > > Every day in every way, I'm progressing more and more! ;-) > You seem to be a bit confused here by the fact that the poky version number lined up with the year in 2017. See https://wiki.yoctoproject.org/wiki/Releases for some context. -- Paul Barker Beta Five Ltd -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
> Take a look at BIOS settings. I had a board that was overclocking based > on CPU temperature, which failed miserably when you actually used all > the cores. Disable such settings. This has nothing to do with this particular problem. You simply, since you over-clocked CPU, reached very quickly TDP1 (using all cores), then reached beyond so-called TDP2 (since you did not setup CMOS correctly), which initiated/triggered HW control called /PROCHOT... In order to save CPU from physical damage, since you have reached very close to Junction T. Even if you did setup thresholds correctly, CPU probably went to hold/blocked state for some limited time to throttle, in order to cool down... Then these YOCTO failing effects might be visible, but I have no idea how (most likely some overheated cores got thread of execution/HyperThreads pipeline stale/lost)!? My best guess, IMHO! Zoran ___ On Fri, Apr 27, 2018 at 2:04 PM, Philip Balister wrote: > On 04/27/2018 02:19 AM, Oliver Graute wrote: >> On 26/04/18, Zoran Stojsavljevic wrote: I deleted all the build-imx6ulevk folder and build everything from scratch with only one thread, waited a few hours for compilation and now its working ;) >>> >>> Still, I am struggling to understand why??? What is the requirement >>> behind this ask? >> >> The requirement was just get our older yocto (jethro) build running on a >> PC of a different developer. Often developers have their own flavor of >> Ubuntu releases and they update to newer versions while they still >> develop on yocto releases which is much older. Because that yocto >> release is currently in the field by our costumer. Our product cycle is >> not so fast to use the newest yocto releases. We started to develop when >> jethro was up to date. >> >> We compiled single threaded just because his PC is a bit unstable on >> high load. And it crashed a few times on parallel makes. I know that >> this is not ideal for yocto development. > > Take a look at BIOS settings. I had a board that was overclocking based > on CPU temperature, which failed miserably when you actually used all > the cores. Disable such settings. > > Philip > > >> >>> >>> As we see, it is much longer (one thread only) than on 14.04!? >> >> its takes much longer then with settings >> >> PARALLEL_MAKE = "-j 4" >> BB_NUMBER_THREADS = "4" >> >>> Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you >>> can't)??? And why, after all??? >> >> currently not im using only Ubuntu LTS Releases. >> Perhaps I will try 18.04 LTS which released yesterday ;) >> >> Best regards, >> >> Oliver >> > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 04/27/2018 02:19 AM, Oliver Graute wrote: > On 26/04/18, Zoran Stojsavljevic wrote: >>> I deleted all the build-imx6ulevk folder and build everything from >>> scratch with only one thread, waited a few hours for compilation and now >>> its working ;) >> >> Still, I am struggling to understand why??? What is the requirement >> behind this ask? > > The requirement was just get our older yocto (jethro) build running on a > PC of a different developer. Often developers have their own flavor of > Ubuntu releases and they update to newer versions while they still > develop on yocto releases which is much older. Because that yocto > release is currently in the field by our costumer. Our product cycle is > not so fast to use the newest yocto releases. We started to develop when > jethro was up to date. > > We compiled single threaded just because his PC is a bit unstable on > high load. And it crashed a few times on parallel makes. I know that > this is not ideal for yocto development. Take a look at BIOS settings. I had a board that was overclocking based on CPU temperature, which failed miserably when you actually used all the cores. Disable such settings. Philip > >> >> As we see, it is much longer (one thread only) than on 14.04!? > > its takes much longer then with settings > > PARALLEL_MAKE = "-j 4" > BB_NUMBER_THREADS = "4" > >> Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you >> can't)??? And why, after all??? > > currently not im using only Ubuntu LTS Releases. > Perhaps I will try 18.04 LTS which released yesterday ;) > > Best regards, > > Oliver > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
> Perhaps I will try 18.04 LTS which released yesterday ;) This will be very interesting test. I bet it'll not work 100% (any of use cases, with any number of threads). Native packages moved far beyond Y2015, far beyond YOCTO Jethro release. Zoran ___ On Fri, Apr 27, 2018 at 8:19 AM, Oliver Graute wrote: > On 26/04/18, Zoran Stojsavljevic wrote: >> > I deleted all the build-imx6ulevk folder and build everything from >> > scratch with only one thread, waited a few hours for compilation and now >> > its working ;) >> >> Still, I am struggling to understand why??? What is the requirement >> behind this ask? > > The requirement was just get our older yocto (jethro) build running on a > PC of a different developer. Often developers have their own flavor of > Ubuntu releases and they update to newer versions while they still > develop on yocto releases which is much older. Because that yocto > release is currently in the field by our costumer. Our product cycle is > not so fast to use the newest yocto releases. We started to develop when > jethro was up to date. > > We compiled single threaded just because his PC is a bit unstable on > high load. And it crashed a few times on parallel makes. I know that > this is not ideal for yocto development. > >> >> As we see, it is much longer (one thread only) than on 14.04!? > > its takes much longer then with settings > > PARALLEL_MAKE = "-j 4" > BB_NUMBER_THREADS = "4" > >> Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you >> can't)??? And why, after all??? > > currently not im using only Ubuntu LTS Releases. > Perhaps I will try 18.04 LTS which released yesterday ;) > > Best regards, > > Oliver > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 26/04/18, Zoran Stojsavljevic wrote: > > I deleted all the build-imx6ulevk folder and build everything from > > scratch with only one thread, waited a few hours for compilation and now > > its working ;) > > Still, I am struggling to understand why??? What is the requirement > behind this ask? The requirement was just get our older yocto (jethro) build running on a PC of a different developer. Often developers have their own flavor of Ubuntu releases and they update to newer versions while they still develop on yocto releases which is much older. Because that yocto release is currently in the field by our costumer. Our product cycle is not so fast to use the newest yocto releases. We started to develop when jethro was up to date. We compiled single threaded just because his PC is a bit unstable on high load. And it crashed a few times on parallel makes. I know that this is not ideal for yocto development. > > As we see, it is much longer (one thread only) than on 14.04!? its takes much longer then with settings PARALLEL_MAKE = "-j 4" BB_NUMBER_THREADS = "4" > Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you > can't)??? And why, after all??? currently not im using only Ubuntu LTS Releases. Perhaps I will try 18.04 LTS which released yesterday ;) Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
> I deleted all the build-imx6ulevk folder and build everything from > scratch with only one thread, waited a few hours for compilation and now > its working ;) Still, I am struggling to understand why??? What is the requirement behind this ask? As we see, it is much longer (one thread only) than on 14.04!? Could you, please, do it on Ubuntu 17.04, or 17.10 (i bet, you can't)??? And why, after all??? Zoran ___ On Thu, Apr 26, 2018 at 5:53 PM, Oliver Graute wrote: > On 25/04/18, Andre McCurdy wrote: >> On Wed, Apr 25, 2018 at 8:03 AM, Oliver Graute >> wrote: >> > Hello list, >> > >> > I try to compile yocto jethro environment which is working >> > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. >> > >> > The compilations stops on gettext-native. >> > >> > bitbake -k fsl-image-mfgtool-initramfs >> > >> > | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a >> > valid libtool object >> >> libgettextsrc_la-message.lo should be a short text file. Could you >> find it in your build tree and post a copy? >> > > the file was a zero byte file. All other *.lo files in that directory > was zero byte too. I assume because of a system crash I had before. > > Just a bitbake -c cleansstate and rebuild of gettext-native didn't fixed that. > > I deleted all the build-imx6ulevk folder and build everything from > scratch with only one thread, waited a few hours for compilation and now > its working ;) > >> > Some ideas whats the cause for this error? >> >> At a guess, something a little unusual with the setup of your Kubuntu >> system. Combining Ubuntu 16.04 with OE 2.0 isn't so out of the >> ordinary and others would certainly have hit the problem before now if >> it was always seen. >> >> Did you install all the standard host dependencies? >> >> >> https://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html#packages >> > > yes but thanks for the link as reference. > > Best regards, > > Oliver > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 25/04/18, Andre McCurdy wrote: > On Wed, Apr 25, 2018 at 8:03 AM, Oliver Graute > wrote: > > Hello list, > > > > I try to compile yocto jethro environment which is working > > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. > > > > The compilations stops on gettext-native. > > > > bitbake -k fsl-image-mfgtool-initramfs > > > > | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a > > valid libtool object > > libgettextsrc_la-message.lo should be a short text file. Could you > find it in your build tree and post a copy? > the file was a zero byte file. All other *.lo files in that directory was zero byte too. I assume because of a system crash I had before. Just a bitbake -c cleansstate and rebuild of gettext-native didn't fixed that. I deleted all the build-imx6ulevk folder and build everything from scratch with only one thread, waited a few hours for compilation and now its working ;) > > Some ideas whats the cause for this error? > > At a guess, something a little unusual with the setup of your Kubuntu > system. Combining Ubuntu 16.04 with OE 2.0 isn't so out of the > ordinary and others would certainly have hit the problem before now if > it was always seen. > > Did you install all the standard host dependencies? > > > https://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html#packages > yes but thanks for the link as reference. Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On Wed, Apr 25, 2018 at 8:03 AM, Oliver Graute wrote: > Hello list, > > I try to compile yocto jethro environment which is working > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. > > The compilations stops on gettext-native. > > bitbake -k fsl-image-mfgtool-initramfs > > make[5]: Entering directory > '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' > | ../x86_64-linux-libtool --tag=CC --mode=link gcc > -isystem/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/include > -O2 -pipe -release 0.19.4 ../gnulib-lib/libgettextlib.la -lc -no-undefined > -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib > -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib > -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib > > -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib > > -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib > -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib > -Wl,-O1 -o libgettextsrc.la -rpath > /home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib > libgettextsrc_la-message.lo libgettextsrc_la-po-error.lo > libgettextsrc_la-po-xerror.lo libgettextsrc_la-read-catalog-abstract.lo > libgettextsrc_la-po-lex.lo libgettextsrc_la-po-gram-gen.lo > libgettextsrc_la-po-charset.lo libgett ex > tsrc_la-read-po.lo libgettextsrc_la-read-properties.lo > libgettextsrc_la-read-stringtable.lo libgettextsrc_la-open-catalog.lo > libgettextsrc_la-dir-list.lo libgettextsrc_la-str-list.lo > libgettextsrc_la-read-catalog.lo libgettextsrc_la-color.lo > libgettextsrc_la-write-catalog.lo libgettextsrc_la-write-properties.lo > libgettextsrc_la-write-stringtable.lo libgettextsrc_la-write-po.lo > libgettextsrc_la-msgl-ascii.lo libgettextsrc_la-msgl-iconv.lo > libgettextsrc_la-msgl-equal.lo libgettextsrc_la-msgl-cat.lo > libgettextsrc_la-msgl-header.lo libgettextsrc_la-msgl-english.lo > libgettextsrc_la-msgl-check.lo libgettextsrc_la-file-list.lo > libgettextsrc_la-msgl-charset.lo libgettextsrc_la-po-time.lo > libgettextsrc_la-plural-exp.lo libgettextsrc_la-plural-eval.lo > libgettextsrc_la-plural-table.lo libgettextsrc_la-format.lo > libgettextsrc_la-format-c.lo libgettextsrc_la-format-sh.lo > libgettextsrc_la-format-python.lo libgettextsrc_la-format-python-brace.lo > libgettextsrc_la-format-lisp.lo libgettext sr > c_la-format-elisp.lo libgettextsrc_la-format-librep.lo > libgettextsrc_la-format-scheme.lo libgettextsrc_la-format-java.lo > libgettextsrc_la-format-csharp.lo libgettextsrc_la-format-awk.lo > libgettextsrc_la-format-pascal.lo libgettextsrc_la-format-ycp.lo > libgettextsrc_la-format-tcl.lo libgettextsrc_la-format-perl.lo > libgettextsrc_la-format-perl-brace.lo libgettextsrc_la-format-php.lo > libgettextsrc_la-format-gcc-internal.lo > libgettextsrc_la-format-gfc-internal.lo libgettextsrc_la-format-qt.lo > libgettextsrc_la-format-qt-plural.lo libgettextsrc_la-format-kde.lo > libgettextsrc_la-format-boost.lo libgettextsrc_la-format-lua.lo > libgettextsrc_la-format-javascript.lo libgettextsrc_la-read-desktop.lo > | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a valid > libtool object libgettextsrc_la-message.lo should be a short text file. Could you find it in your build tree and post a copy? > | Makefile:2285: recipe for target 'libgettextsrc.la' failed > | make[5]: *** [libgettextsrc.la] Error 1 > | make[5]: Leaving directory > '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' > | Makefile:2206: recipe for target 'all' failed > | make[4]: *** [all] Error 2 > | make[4]: Leaving directory > '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' > | Makefile:1698: recipe for target 'all-recursive' failed > | make[3]: *** [all-recursive] Error 1 > | make[3]: Leaving directory > '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools' > | Makefile:1564: recipe for target 'all' failed > | make[2]: *** [all] Error 2 > | make[2]: Leaving directory > '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools' > | Makefile:380: recipe for target 'all-recursive' failed > | make[1]: *** [all-recursive] Error 1 > | make[1]: Leaving directory > '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build' > | Makefile:336: recipe for target 'all' failed > | make: *** [all] Error 2 > | ERROR: oe_runmake failed > | ERROR: Function failed: do_compile (log file is located at > /home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/temp/log.do_compile.5336) > ERROR: Task 531 > (virtual:native:/home/us/build/os-poky/meta/recipes-core/gettext/gettext_0.19.4.bb, > do_compile) failed wi
Re: [yocto] yocto jethro failed on gettext-native
Oliver, Sorry for stealing your show... Did not want to. :-( Floor all yours. Zoran ___ On Wed, Apr 25, 2018 at 10:55 PM, Zoran Stojsavljevic wrote: >> Jethro doesn't support Yocto 16.* because it is very old (released >> 2015...)... > > Now, I must admit, I have learned something new. Never gave any > consideration to these releases: example: Pyro 17.0.3. > > But now I understand: it has direct link with Ubuntu 17... Even, YOCTO > Pyro, as given example, can be substituted with Ubuntu 17.04?! Wow... > > Every day in every way, I'm progressing more and more! ;-) > >> If you want to use Jethro despite the known serious security problems >> then you'll need to dig out the relevant fixes from the newer releases. > > My question here is: how hard it is? Either to move/rebase complex > application and some system packages to Rocko (and rebase/revisit > APIs), either to back-port additional (security) packages from the > newer releases?! > > Seems lot of hard work, considering both cases. > > Zoran > > On Wed, Apr 25, 2018 at 9:50 PM, Burton, Ross wrote: >> Jethro doesn't support Yocto 16.* because it is very old (released >> 2015, it's been unmaintained for six months now). If you want to use >> Jethro despite the known serious security problems then you'll need to >> dig out the relevant fixes from the newer releases. >> >> Ross >> >> On 25 April 2018 at 20:36, Oliver Graute wrote: >>> On 25/04/18, Zoran Stojsavljevic wrote: > I try to compile yocto jethro environment which is working > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . What would be the benefit for the successful compiling of YOCTO Jethro on Kubuntu 16.04 over Ubuntu 14.04??? >>> >>> I tried to get my Yocto compiled on a PC of a colleague and his >>> installation was a Kubuntu 16.04. I've made the experience that often >>> only additional packages needs to be installed to step over these >>> compile issues. Sometimes its clear from the debug output but in this >>> case I have no Idea which packages is missing. On my develop PC and our >>> Buildserver with Ubuntu 14.04 everything is fine. But I'am afraid that I >>> can get similar trouble if I update to a newer ubuntu release there too. >>> >>> Best regards, >>> >>> Oliver >>> -- >>> ___ >>> yocto mailing list >>> yocto@yoctoproject.org >>> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
> Jethro doesn't support Yocto 16.* because it is very old (released 2015...)... Now, I must admit, I have learned something new. Never gave any consideration to these releases: example: Pyro 17.0.3. But now I understand: it has direct link with Ubuntu 17... Even, YOCTO Pyro, as given example, can be substituted with Ubuntu 17.04?! Wow... Every day in every way, I'm progressing more and more! ;-) > If you want to use Jethro despite the known serious security problems > then you'll need to dig out the relevant fixes from the newer releases. My question here is: how hard it is? Either to move/rebase complex application and some system packages to Rocko (and rebase/revisit APIs), either to back-port additional (security) packages from the newer releases?! Seems lot of hard work, considering both cases. Zoran On Wed, Apr 25, 2018 at 9:50 PM, Burton, Ross wrote: > Jethro doesn't support Yocto 16.* because it is very old (released > 2015, it's been unmaintained for six months now). If you want to use > Jethro despite the known serious security problems then you'll need to > dig out the relevant fixes from the newer releases. > > Ross > > On 25 April 2018 at 20:36, Oliver Graute wrote: >> On 25/04/18, Zoran Stojsavljevic wrote: >>> > I try to compile yocto jethro environment which is working >>> > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . >>> >>> What would be the benefit for the successful compiling of YOCTO Jethro on >>> Kubuntu 16.04 over Ubuntu 14.04??? >> >> I tried to get my Yocto compiled on a PC of a colleague and his >> installation was a Kubuntu 16.04. I've made the experience that often >> only additional packages needs to be installed to step over these >> compile issues. Sometimes its clear from the debug output but in this >> case I have no Idea which packages is missing. On my develop PC and our >> Buildserver with Ubuntu 14.04 everything is fine. But I'am afraid that I >> can get similar trouble if I update to a newer ubuntu release there too. >> >> Best regards, >> >> Oliver >> -- >> ___ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 2018-04-25 03:50 PM, Burton, Ross wrote: Jethro doesn't support Yocto 16.* because it is very old (released Err, Jethro doesn't support _Ubuntu_ 16.* (Yocto 16.* is a ways off! :) ) 2015, it's been unmaintained for six months now). If you want to use Jethro despite the known serious security problems then you'll need to dig out the relevant fixes from the newer releases. Can you use a later release of Yocto such as 2.4 or 2.5 aka rocko/sumo? If you need to use an older release there are companies, such as Wind River [1], that can provide commercial support for 5+ years after the Yocto release date. Send me an email off-list and I'll help you contact our sales people! :) ../Randy [1] https://www.yoctoproject.org/ecosystem/yocto-project-compatible-product-showcase/ This list is a bit out of date, we release WR Linux 10: LTS last fall. It's based on YP-2.4/rocko Ross On 25 April 2018 at 20:36, Oliver Graute wrote: On 25/04/18, Zoran Stojsavljevic wrote: I try to compile yocto jethro environment which is working on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . What would be the benefit for the successful compiling of YOCTO Jethro on Kubuntu 16.04 over Ubuntu 14.04??? I tried to get my Yocto compiled on a PC of a colleague and his installation was a Kubuntu 16.04. I've made the experience that often only additional packages needs to be installed to step over these compile issues. Sometimes its clear from the debug output but in this case I have no Idea which packages is missing. On my develop PC and our Buildserver with Ubuntu 14.04 everything is fine. But I'am afraid that I can get similar trouble if I update to a newer ubuntu release there too. Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- # Randy MacLeod # Wind River Linux -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
Jethro doesn't support Yocto 16.* because it is very old (released 2015, it's been unmaintained for six months now). If you want to use Jethro despite the known serious security problems then you'll need to dig out the relevant fixes from the newer releases. Ross On 25 April 2018 at 20:36, Oliver Graute wrote: > On 25/04/18, Zoran Stojsavljevic wrote: >> > I try to compile yocto jethro environment which is working >> > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . >> >> What would be the benefit for the successful compiling of YOCTO Jethro on >> Kubuntu 16.04 over Ubuntu 14.04??? > > I tried to get my Yocto compiled on a PC of a colleague and his > installation was a Kubuntu 16.04. I've made the experience that often > only additional packages needs to be installed to step over these > compile issues. Sometimes its clear from the debug output but in this > case I have no Idea which packages is missing. On my develop PC and our > Buildserver with Ubuntu 14.04 everything is fine. But I'am afraid that I > can get similar trouble if I update to a newer ubuntu release there too. > > Best regards, > > Oliver > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
On 25/04/18, Zoran Stojsavljevic wrote: > > I try to compile yocto jethro environment which is working > > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . > > What would be the benefit for the successful compiling of YOCTO Jethro on > Kubuntu 16.04 over Ubuntu 14.04??? I tried to get my Yocto compiled on a PC of a colleague and his installation was a Kubuntu 16.04. I've made the experience that often only additional packages needs to be installed to step over these compile issues. Sometimes its clear from the debug output but in this case I have no Idea which packages is missing. On my develop PC and our Buildserver with Ubuntu 14.04 everything is fine. But I'am afraid that I can get similar trouble if I update to a newer ubuntu release there too. Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto jethro failed on gettext-native
> The benefit of the successful compiling of YOCTO Jethro on Kubuntu 16.04 over Ubuntu 14.04 would be the > full understanding of the yocto system and its interaction with the host system. I do buy this argument just for the sole/only one use case: if you try to become YOCTO distro developer by yourself! ;-) Zoran ___ On Wed, Apr 25, 2018 at 8:13 PM, Jean-Pierre Sainfeld wrote: > The benefit of the successful compiling of YOCTO Jethro on Kubuntu 16.04 > over Ubuntu 14.04 would be the > full understanding of the yocto system and its interaction with the host > system. > Yocto is a fantastic tool albeit a large piece of knowledge to swallow :-) > > JP Sainfeld > > On Wed, Apr 25, 2018 at 10:49 AM, Zoran Stojsavljevic < > zoran.stojsavlje...@gmail.com> wrote: > >> > I try to compile yocto jethro environment which is working >> > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . >> >> What would be the benefit for the successful compiling of YOCTO Jethro on >> Kubuntu 16.04 over Ubuntu 14.04??? >> >> Zoran >> ___ >> >> On Wed, Apr 25, 2018 at 5:03 PM, Oliver Graute >> wrote: >> >>> Hello list, >>> >>> I try to compile yocto jethro environment which is working >>> on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. >>> >>> The compilations stops on gettext-native. >>> >>> bitbake -k fsl-image-mfgtool-initramfs >>> >>> make[5]: Entering directory '/home/us/build-imx6ulevk-mfgt >>> ool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/get >>> text-tools/src' >>> | ../x86_64-linux-libtool --tag=CC --mode=link gcc >>> >>> -isystem/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/include >>> -O2 -pipe -release 0.19.4 ../gnulib-lib/libgettextlib.la -lc >>> -no-undefined -L/home/us/build-imx6ulevk-mfg >>> tool/tmp/sysroots/x86_64-linux/usr/lib -L/home/us/build-imx6ulevk-mfg >>> tool/tmp/sysroots/x86_64-linux/lib -Wl,-rpath-link,/home/us/build >>> -imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib >>> -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib >>> -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib >>> -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib >>> -Wl,-O1 -o libgettextsrc.la -rpath /home/us/build-imx6ulevk-mfgto >>> ol/tmp/sysroots/x86_64-linux/usr/lib libgettextsrc_la-message.lo >>> libgettextsrc_la-po-error.lo libgettextsrc_la-po-xerror.lo >>> libgettextsrc_la-read-catalog-abstract.lo libgettextsrc_la-po-lex.lo >>> libgettextsrc_la-po-gram-gen.lo libgettextsrc_la-po-charset.lo libgettex >>> tsrc_la-read-po.lo libgettextsrc_la-read-properties.lo >>> libgettextsrc_la-read-stringtable.lo libgettextsrc_la-open-catalog.lo >>> libgettextsrc_la-dir-list.lo libgettextsrc_la-str-list.lo >>> libgettextsrc_la-read-catalog.lo libgettextsrc_la-color.lo >>> libgettextsrc_la-write-catalog.lo libgettextsrc_la-write-properties.lo >>> libgettextsrc_la-write-stringtable.lo libgettextsrc_la-write-po.lo >>> libgettextsrc_la-msgl-ascii.lo libgettextsrc_la-msgl-iconv.lo >>> libgettextsrc_la-msgl-equal.lo libgettextsrc_la-msgl-cat.lo >>> libgettextsrc_la-msgl-header.lo libgettextsrc_la-msgl-english.lo >>> libgettextsrc_la-msgl-check.lo libgettextsrc_la-file-list.lo >>> libgettextsrc_la-msgl-charset.lo libgettextsrc_la-po-time.lo >>> libgettextsrc_la-plural-exp.lo libgettextsrc_la-plural-eval.lo >>> libgettextsrc_la-plural-table.lo libgettextsrc_la-format.lo >>> libgettextsrc_la-format-c.lo libgettextsrc_la-format-sh.lo >>> libgettextsrc_la-format-python.lo libgettextsrc_la-format-python-brace.lo >>> libgettextsrc_la-format-lisp.lo libgettextsr >>> c_la-format-elisp.lo libgettextsrc_la-format-librep.lo >>> libgettextsrc_la-format-scheme.lo libgettextsrc_la-format-java.lo >>> libgettextsrc_la-format-csharp.lo libgettextsrc_la-format-awk.lo >>> libgettextsrc_la-format-pascal.lo libgettextsrc_la-format-ycp.lo >>> libgettextsrc_la-format-tcl.lo libgettextsrc_la-format-perl.lo >>> libgettextsrc_la-format-perl-brace.lo libgettextsrc_la-format-php.lo >>> libgettextsrc_la-format-gcc-internal.lo >>> libgettextsrc_la-format-gfc-internal.lo >>> libgettextsrc_la-format-qt.lo libgettextsrc_la-format-qt-plural.lo >>> libgettextsrc_la-format-kde.lo libgettextsrc_la-format-boost.lo >>> libgettextsrc_la-format-lua.lo libgettextsrc_la-format-javascript.lo >>> libgettextsrc_la-read-desktop.lo >>> | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a >>> valid libtool object >>> | Makefile:2285: recipe for target 'libgettextsrc.la' failed >>> | make[5]: *** [libgettextsrc.la] Error 1 >>> | make[5]: Leaving directory '/home/us/build-imx6ulevk-mfgt >>> ool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/get >>> text-tools/src' >>> | Makefile:2206: recipe for target 'all' failed >>> | make[4]: *** [all] Error 2 >>> | make[4]: Leaving directory '/home/us/build-imx6ulevk-mfgt >>> ool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/get >>> text-tools/src' >>> | Makefile:1698: recipe for
Re: [yocto] yocto jethro failed on gettext-native
> I try to compile yocto jethro environment which is working > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 . What would be the benefit for the successful compiling of YOCTO Jethro on Kubuntu 16.04 over Ubuntu 14.04??? Zoran ___ On Wed, Apr 25, 2018 at 5:03 PM, Oliver Graute wrote: > Hello list, > > I try to compile yocto jethro environment which is working > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. > > The compilations stops on gettext-native. > > bitbake -k fsl-image-mfgtool-initramfs > > make[5]: Entering directory '/home/us/build-imx6ulevk- > mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/ > build/gettext-tools/src' > | ../x86_64-linux-libtool --tag=CC --mode=link gcc > > -isystem/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/include > -O2 -pipe -release 0.19.4 ../gnulib-lib/libgettextlib.la -lc > -no-undefined > -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib > -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib > -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib > -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib > -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib > -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib > -Wl,-O1 -o libgettextsrc.la -rpath /home/us/build-imx6ulevk- > mfgtool/tmp/sysroots/x86_64-linux/usr/lib libgettextsrc_la-message.lo > libgettextsrc_la-po-error.lo libgettextsrc_la-po-xerror.lo > libgettextsrc_la-read-catalog-abstract.lo libgettextsrc_la-po-lex.lo > libgettextsrc_la-po-gram-gen.lo libgettextsrc_la-po-charset.lo libgettex > tsrc_la-read-po.lo libgettextsrc_la-read-properties.lo > libgettextsrc_la-read-stringtable.lo libgettextsrc_la-open-catalog.lo > libgettextsrc_la-dir-list.lo libgettextsrc_la-str-list.lo > libgettextsrc_la-read-catalog.lo libgettextsrc_la-color.lo > libgettextsrc_la-write-catalog.lo libgettextsrc_la-write-properties.lo > libgettextsrc_la-write-stringtable.lo libgettextsrc_la-write-po.lo > libgettextsrc_la-msgl-ascii.lo libgettextsrc_la-msgl-iconv.lo > libgettextsrc_la-msgl-equal.lo libgettextsrc_la-msgl-cat.lo > libgettextsrc_la-msgl-header.lo libgettextsrc_la-msgl-english.lo > libgettextsrc_la-msgl-check.lo libgettextsrc_la-file-list.lo > libgettextsrc_la-msgl-charset.lo libgettextsrc_la-po-time.lo > libgettextsrc_la-plural-exp.lo libgettextsrc_la-plural-eval.lo > libgettextsrc_la-plural-table.lo libgettextsrc_la-format.lo > libgettextsrc_la-format-c.lo libgettextsrc_la-format-sh.lo > libgettextsrc_la-format-python.lo libgettextsrc_la-format-python-brace.lo > libgettextsrc_la-format-lisp.lo libgettextsr > c_la-format-elisp.lo libgettextsrc_la-format-librep.lo > libgettextsrc_la-format-scheme.lo libgettextsrc_la-format-java.lo > libgettextsrc_la-format-csharp.lo libgettextsrc_la-format-awk.lo > libgettextsrc_la-format-pascal.lo libgettextsrc_la-format-ycp.lo > libgettextsrc_la-format-tcl.lo libgettextsrc_la-format-perl.lo > libgettextsrc_la-format-perl-brace.lo libgettextsrc_la-format-php.lo > libgettextsrc_la-format-gcc-internal.lo > libgettextsrc_la-format-gfc-internal.lo > libgettextsrc_la-format-qt.lo libgettextsrc_la-format-qt-plural.lo > libgettextsrc_la-format-kde.lo libgettextsrc_la-format-boost.lo > libgettextsrc_la-format-lua.lo libgettextsrc_la-format-javascript.lo > libgettextsrc_la-read-desktop.lo > | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a > valid libtool object > | Makefile:2285: recipe for target 'libgettextsrc.la' failed > | make[5]: *** [libgettextsrc.la] Error 1 > | make[5]: Leaving directory '/home/us/build-imx6ulevk- > mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/ > build/gettext-tools/src' > | Makefile:2206: recipe for target 'all' failed > | make[4]: *** [all] Error 2 > | make[4]: Leaving directory '/home/us/build-imx6ulevk- > mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/ > build/gettext-tools/src' > | Makefile:1698: recipe for target 'all-recursive' failed > | make[3]: *** [all-recursive] Error 1 > | make[3]: Leaving directory '/home/us/build-imx6ulevk- > mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/ > build/gettext-tools' > | Makefile:1564: recipe for target 'all' failed > | make[2]: *** [all] Error 2 > | make[2]: Leaving directory '/home/us/build-imx6ulevk- > mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/ > build/gettext-tools' > | Makefile:380: recipe for target 'all-recursive' failed > | make[1]: *** [all-recursive] Error 1 > | make[1]: Leaving directory '/home/us/build-imx6ulevk- > mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build' > | Makefile:336: recipe for target 'all' failed > | make: *** [all] Error 2 > | ERROR: oe_runmake failed > | ERROR: Function failed: do_compile (log file is located at > /home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/ > gettext-native/0.19.4-r0/temp/log.do_compile.5336) > ERROR: Task 531
[yocto] yocto jethro failed on gettext-native
Hello list, I try to compile yocto jethro environment which is working on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04. The compilations stops on gettext-native. bitbake -k fsl-image-mfgtool-initramfs make[5]: Entering directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' | ../x86_64-linux-libtool --tag=CC --mode=link gcc -isystem/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -release 0.19.4 ../gnulib-lib/libgettextlib.la -lc -no-undefined -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib -L/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath-link,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath,/home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/lib -Wl,-O1 -o libgettextsrc.la -rpath /home/us/build-imx6ulevk-mfgtool/tmp/sysroots/x86_64-linux/usr/lib libgettextsrc_la-message.lo libgettextsrc_la-po-error.lo libgettextsrc_la-po-xerror.lo libgettextsrc_la-read-catalog-abstract.lo libgettextsrc_la-po-lex.lo libgettextsrc_la-po-gram-gen.lo libgettextsrc_la-po-charset.lo libgettex tsrc_la-read-po.lo libgettextsrc_la-read-properties.lo libgettextsrc_la-read-stringtable.lo libgettextsrc_la-open-catalog.lo libgettextsrc_la-dir-list.lo libgettextsrc_la-str-list.lo libgettextsrc_la-read-catalog.lo libgettextsrc_la-color.lo libgettextsrc_la-write-catalog.lo libgettextsrc_la-write-properties.lo libgettextsrc_la-write-stringtable.lo libgettextsrc_la-write-po.lo libgettextsrc_la-msgl-ascii.lo libgettextsrc_la-msgl-iconv.lo libgettextsrc_la-msgl-equal.lo libgettextsrc_la-msgl-cat.lo libgettextsrc_la-msgl-header.lo libgettextsrc_la-msgl-english.lo libgettextsrc_la-msgl-check.lo libgettextsrc_la-file-list.lo libgettextsrc_la-msgl-charset.lo libgettextsrc_la-po-time.lo libgettextsrc_la-plural-exp.lo libgettextsrc_la-plural-eval.lo libgettextsrc_la-plural-table.lo libgettextsrc_la-format.lo libgettextsrc_la-format-c.lo libgettextsrc_la-format-sh.lo libgettextsrc_la-format-python.lo libgettextsrc_la-format-python-brace.lo libgettextsrc_la-format-lisp.lo libgettextsr c_la-format-elisp.lo libgettextsrc_la-format-librep.lo libgettextsrc_la-format-scheme.lo libgettextsrc_la-format-java.lo libgettextsrc_la-format-csharp.lo libgettextsrc_la-format-awk.lo libgettextsrc_la-format-pascal.lo libgettextsrc_la-format-ycp.lo libgettextsrc_la-format-tcl.lo libgettextsrc_la-format-perl.lo libgettextsrc_la-format-perl-brace.lo libgettextsrc_la-format-php.lo libgettextsrc_la-format-gcc-internal.lo libgettextsrc_la-format-gfc-internal.lo libgettextsrc_la-format-qt.lo libgettextsrc_la-format-qt-plural.lo libgettextsrc_la-format-kde.lo libgettextsrc_la-format-boost.lo libgettextsrc_la-format-lua.lo libgettextsrc_la-format-javascript.lo libgettextsrc_la-read-desktop.lo | x86_64-linux-libtool: error: 'libgettextsrc_la-message.lo' is not a valid libtool object | Makefile:2285: recipe for target 'libgettextsrc.la' failed | make[5]: *** [libgettextsrc.la] Error 1 | make[5]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' | Makefile:2206: recipe for target 'all' failed | make[4]: *** [all] Error 2 | make[4]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools/src' | Makefile:1698: recipe for target 'all-recursive' failed | make[3]: *** [all-recursive] Error 1 | make[3]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools' | Makefile:1564: recipe for target 'all' failed | make[2]: *** [all] Error 2 | make[2]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build/gettext-tools' | Makefile:380: recipe for target 'all-recursive' failed | make[1]: *** [all-recursive] Error 1 | make[1]: Leaving directory '/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/build' | Makefile:336: recipe for target 'all' failed | make: *** [all] Error 2 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (log file is located at /home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-linux/gettext-native/0.19.4-r0/temp/log.do_compile.5336) ERROR: Task 531 (virtual:native:/home/us/build/os-poky/meta/recipes-core/gettext/gettext_0.19.4.bb, do_compile) failed with exit code '1' I already tried to reinstall libtool but without success. Some ideas whats the cause for this error? Best regards, Oliver -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
