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

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:

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

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

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,

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?

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)

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

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

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,

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,

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

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,

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

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

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

[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