Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-08-24
Date: Tue, 25 Aug 2015 08:35:45 -0300	[thread overview]
Message-ID: <55DC5311.4000500@zacarias.com.ar> (raw)
In-Reply-To: <20150825125744.406bc9c1@free-electrons.com>

On 25/08/15 07:57, Thomas Petazzoni wrote:

>>>>>      mips64el |                   midori-0.5.9 | NOK | http://autobuild.buildroot.net/results/80ffdf54fd675fbff5a645784cd041cdf862154c/
>>>>>      mips64el |                   midori-0.5.9 | NOK | http://autobuild.buildroot.net/results/1c049845ade60de223296c77c8a70869c4db64f0/
>>>>
>>>> Currently investigating.
>>>
>>> Thanks!
>>
>> And cannot reproduce it :/ Sorry, let's see if future build reports
>> still hightlight this failure.
>
> Well:
>
> --   package 'webkit2gtk-3.0>=1.11.91' not found
> --   package 'javascriptcoregtk-3.0' not found
>
> and we don't have webkit2gtk-3.0, we only have webkit2gtk. But I'm a
> bit surprised, since Gustavo bumped webkitgtk and midori at the same
> time. Gustavo, can you have a look?

webkit2gtk-3.0 means webkit API 2 (new) for gtk 3, which is correct 
since the config has libgtk3 enabled.
This curious naming is used so that multiple variants can live 
side-by-side (different screen rendering backends and APIs).
I'll give it a look.
Regards.

      reply	other threads:[~2015-08-25 11:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-08-24 Thomas Petazzoni
2015-08-25 10:25 ` Vicente Olivert Riera
2015-08-25 10:39   ` Thomas Petazzoni
2015-08-25 10:46     ` Vicente Olivert Riera
2015-08-25 10:57       ` Thomas Petazzoni
2015-08-25 11:35         ` Gustavo Zacarias [this message]

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=55DC5311.4000500@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox