All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riko Ho <antonius.riko@gmail.com>
To: Takuro Ashie <ashie@clear-code.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ?
Date: Tue, 4 Jul 2017 13:16:50 +0800	[thread overview]
Message-ID: <8692e969-0575-1a75-b0a7-1567bcb51786@gmail.com> (raw)
In-Reply-To: <d1fc68c9-0a41-ac45-161d-68d34f1f2e18@clear-code.com>

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

I got this error :

checking for autoconf...
| ERROR: Could not find autoconf 2.13
| *** Fix above errors and then restart with\
|                "make -f client.mk build"
| client.mk:375: recipe for target 'configure' failed
| make: *** [configure] Error 1
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure

How to fix it ? thanks. I'm using Ubuntu 16.04 as a host.


On 03/07/17 15:32, Takuro Ashie wrote:
> Hi.
>
>> How can I update to the latest firefox version?
>>
>> /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb
>>
>
> I'm now trying to upgrade it to 52ESR:
>
> https://github.com/OSSystems/meta-browser/pull/43
>
> It almost done but seems have a problem. Drawing tabs may be broken.
> I'm now investigating it.
> If you are interesting it, please try the following branch and report 
> issues:
>
> https://github.com/ashie/meta-browser/tree/firefox-52.1.2esr-2
>
> In addition, we are also trying to support
>
>   * Wayland
>   * OpenMAX
>   * EGL
>
> They are already enabled in the following branch but not stable yet:
>
> https://github.com/mozilla-japan/meta-browser/tree/firefox-52.2esr
>
> Regards,
> Takuro Ashie <ashie@clear-code.com>
>
>
> On 2017年07月01日 15:03, Riko Ho wrote:
>>
>> Hello Everyone,
>>
>> How can I update to the latest firefox version?
>>
>> /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb
>>
>> Thanks
>> -- 
>> *
>>
>> /*******/
>> Sent by Ubuntu LTS 16.04,
>> Kind regards,
>> Riko Ho
>> /*******/
>>
>> *
>>
>>
>

-- 
*

/*******/
Sent by Ubuntu LTS 16.04,
Kind regards,
Riko Ho
/*******/

*

[-- Attachment #2: Type: text/html, Size: 3881 bytes --]

  parent reply	other threads:[~2017-07-04  5:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23  8:18 internet radio Riko Ho
2017-06-23 13:42 ` Khem Raj
2017-06-24  4:42   ` RTL8192EU question ? Riko Ho
2017-06-24  4:58   ` internet radio Riko Ho
2017-06-24  5:00   ` Riko Ho
2017-06-24  6:04   ` Riko Ho
2017-06-28  3:11   ` Riko Ho
2017-07-01  6:03   ` /poky/meta-browser/recipes-mozilla/firefox/firefox_45.9.0esr.bb =>how to update the newest version ? Riko Ho
2017-07-03  7:32     ` Takuro Ashie
2017-07-03  8:04       ` Riko Ho
2017-07-04  5:16       ` Riko Ho [this message]
2017-07-04  5:33         ` Takuro Ashie
2017-07-04  5:34           ` Riko Ho
2017-07-04  5:40           ` Riko Ho
2017-07-04  6:34             ` Takuro Ashie
2017-07-04  6:43               ` Takuro Ashie
2017-07-04  7:00                 ` Riko Ho
2017-07-04  7:03                   ` Takuro Ashie
2017-07-04  7:12                     ` Riko Ho
2017-07-04  7:16                     ` Riko Ho
2017-07-04  8:06                     ` Riko Ho
2017-07-04  9:51                       ` Takuro Ashie
2017-07-05  2:15                         ` Riko Ho

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=8692e969-0575-1a75-b0a7-1567bcb51786@gmail.com \
    --to=antonius.riko@gmail.com \
    --cc=ashie@clear-code.com \
    --cc=yocto@yoctoproject.org \
    /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.