All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riko Ho <antonius.riko@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Compiling meta-browser ==>chromium ? cleaning ?
Date: Sun, 18 Jun 2017 15:52:19 +0800	[thread overview]
Message-ID: <104e49b0-c604-4cba-0a26-da256e2fb180@gmail.com> (raw)
In-Reply-To: <CA+chaQcwEW7=Wmrk0LYN0ubfvwxTNZQnCDh=wwWRWmSaXgWJdg@mail.gmail.com>

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

What version are you talking about ? how can I know that ?

Thanks


On 18/06/17 15:49, Martin Jansa wrote:
> You didn't say which versions you're using.
>
> If you're using latest oe-core with gcc7 then you will need v3 version 
> of this change:
> http://lists.openembedded.org/pipermail/openembedded-devel/2017-June/113247.html
> I'll send it later today.
>
> > And how can I clean after building it ? It took about 70Gb of my drive
>
> Like any other recipe:
> bitbake -c clean foo
>
> On Sun, Jun 18, 2017 at 1:41 AM, Riko Ho <antonius.riko@gmail.com 
> <mailto:antonius.riko@gmail.com>> wrote:
>
>     Hello Everyone,
>
>     I tried to compile chromium but never succeeded, took me already
>     12 hours and stopped on 99%,
>     I used bitbake for doing it,
>
>     Is chromium not compatible with arm CPU ? it was working with
>     X86_64 before.
>     And how can I clean after building it ? It took about 70Gb of my drive
>
>     Thanks
>     -- 
>     _______________________________________________
>     yocto mailing list
>     yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/yocto
>     <https://lists.yoctoproject.org/listinfo/yocto>
>
>

-- 
*

/*******/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/*******/

*

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

  reply	other threads:[~2017-06-18  7:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  4:10 bitbake core-image-web-kiosk question ? Riko Ho
2017-06-14  5:38 ` Khem Raj
2017-06-15  5:53   ` FriendlyArm Mini6410 ? Riko Ho
2017-06-15  6:05     ` Belisko Marek
2017-06-15  7:16       ` Riko Ho
2017-06-16  1:32       ` Image type on bitbake ? Riko Ho
2017-06-17 23:41       ` Compiling meta-browser ==>chromium ? cleaning ? Riko Ho
2017-06-18  7:49         ` Martin Jansa
2017-06-18  7:52           ` Riko Ho [this message]
2017-06-18 11:48           ` dd image to sdcard ? Riko Ho
2017-06-18 19:17             ` Burton, Ross
2017-06-18 19:37               ` Maciej Borzęcki
2017-06-18 22:03                 ` Riko Ho
2017-06-19  3:00           ` RTL8192EU rev B (SMIC) ==> rtl8192eu_nic.bin ? Riko Ho
2017-06-19 19:57             ` Khem Raj
2017-06-20  3:35               ` Riko Ho
2017-06-20  3:46               ` Riko Ho
2017-06-20  4:51                 ` Khem Raj
2017-06-21  1:52                   ` Riko Ho
2017-06-21  2:28                     ` Khem Raj
2017-06-21  2:32                       ` Riko Ho
     [not found] <mailman.66247.1497786545.15860.yocto@yoctoproject.org>
2017-06-18 18:10 ` Compiling meta-browser ==>chromium ? cleaning ? Gunnar Andersson
2017-06-19 14:21   ` Jacobo Aragunde Pérez
2017-06-19 20:01     ` Khem Raj
2017-06-20  3:32       ` Riko Ho
2017-06-20  5:08         ` Khem Raj
2017-06-21  1:53           ` Riko Ho
2017-06-21  2:28             ` Khem Raj
2017-06-21  4:38               ` Riko Ho
2017-06-21  4:42               ` Riko Ho
2017-06-21  7:37                 ` Gunnar Andersson
2017-06-21  8:18                   ` Riko Ho
2017-06-21  8:24                   ` Riko Ho
2017-06-24  4:52                   ` 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=104e49b0-c604-4cba-0a26-da256e2fb180@gmail.com \
    --to=antonius.riko@gmail.com \
    --cc=martin.jansa@gmail.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.