All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Zoran Stojsavljevic <zoran.stojsavljevic@gmail.com>,
	Yocto Project <yocto@yoctoproject.org>
Subject: Re: yocto jethro failed on gettext-native
Date: Wed, 25 Apr 2018 20:50:35 +0100	[thread overview]
Message-ID: <CAJTo0LZ5Cf5zqLVJf+Jjd60KLLKJ2q-01B3QdpuVDGx4tCxKAg@mail.gmail.com> (raw)
In-Reply-To: <5ae0d8b5.3bb5500a.22ed7.1ad6@mx.google.com>

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 <oliver.graute@gmail.com> 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


  reply	other threads:[~2018-04-25 19:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 15:03 yocto jethro failed on gettext-native Oliver Graute
2018-04-25 17:49 ` Zoran Stojsavljevic
     [not found]   ` <CAEv37YsacVBmZXtShCij9OxkXmQpUX92QnS=tg_ESO_0NkT3ow@mail.gmail.com>
2018-04-25 18:27     ` Zoran Stojsavljevic
2018-04-25 19:36   ` Oliver Graute
2018-04-25 19:50     ` Burton, Ross [this message]
2018-04-25 20:49       ` Randy MacLeod
2018-04-25 20:55       ` Zoran Stojsavljevic
2018-04-25 20:58         ` Zoran Stojsavljevic
2018-05-02 20:36         ` Paul Barker
2018-05-03  3:29           ` Zoran Stojsavljevic
2018-04-26  4:07 ` Andre McCurdy
2018-04-26 15:53   ` Oliver Graute
2018-04-26 17:33     ` Zoran Stojsavljevic
2018-04-27  6:19       ` Oliver Graute
2018-04-27  9:25         ` Zoran Stojsavljevic
2018-04-27 12:04         ` Philip Balister
2018-04-27 13:27           ` Zoran Stojsavljevic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJTo0LZ5Cf5zqLVJf+Jjd60KLLKJ2q-01B3QdpuVDGx4tCxKAg@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=yocto@yoctoproject.org \
    --cc=zoran.stojsavljevic@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.