All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-browser] CFT: Chromium 62 in meta-browser
Date: Wed, 15 Nov 2017 18:41:36 +0100	[thread overview]
Message-ID: <20171115174136.GA4530@jama> (raw)
In-Reply-To: <877eur1nby.fsf@rkubodac-desk.ger.corp.intel.com>

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

On Wed, Nov 15, 2017 at 06:08:49PM +0100, Raphael Kubo da Costa wrote:
> Thanks for testing!
> 
> Martin Jansa <martin.jansa@gmail.com> writes:
> > Thanks for very good changes.
> >
> > Yesterday I've tried to build this on "bitbake world" servers and the build
> > for qemuarm64 failed with:
> [...]
> > longer log in http://errors.yoctoproject.org/Errors/Details/158898/
> [...]
> > I know what linking needs *a lot* of memory, but this server has 219GB
> > available and "only" 128GB from it can be taken by tmpfs, so there should
> > be still plenty RAM for successful linkage.
> 
> It had been a while since I'd last done an aarch64 build. I launched one
> here and linking failed with relocation errors. I've pushed 4e5abf8
> ("chromium: Apply -g -> -g1 workaround for aarch64 as well"), which is
> the same workaround I've been applying for other architectures, and
> everything went fine.

With the latest version from you (62.0.3202.94) I also got relocation
errors instead of the out-of-memory one, see:

http://errors.yoctoproject.org/Errors/Build/48426/

I'm trying now with g1 as you suggested.

> 
> > Build for x86_64 (on similar server) was successful.
> >
> > Build for x86 + musl failed even before start, because there is missing
> > space in the append:
> > recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86 =
> > "yasm-native"
> > recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_x86-64 =
> > "yasm-native"
> >
> > and unlike x86_64 it doesn't have trailing space in previous DEPENDS,
> > because of:
> > recipes-browser/chromium/chromium_62.0.3202.89.bb:DEPENDS_append_libc-musl
> > = " libexecinfo"
> >
> > Causing:
> > ERROR: Nothing PROVIDES 'libexecinfoyasm-native' (but
> > /home/jenkins/oe/world/shr-core/meta-browser/recipes-browser/chromium/
> > chromium_62.0.3202.89.bb DEPENDS on or otherwise requires it). Close
> > matches:
> >   libxinerama-native
> >   texinfo-native
> >   libyaml-native
> 
> Thanks for fixing the yasm bit.
> 
> As for musl: like I said in my original email and on GitHub, the musl
> build is currently broken. Carrying tons of patches in the recipe is an
> uphill battle, so unless someone takes the time to work with upstream I
> don't think it makes much sense to try to keep the build working.

OK, fair enough, maybe Khem will again chime in and fix it for musl (in
the meantime we might blacklist it for musl that people don't wait for
the build to fail).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2017-11-15 17:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 16:28 [meta-browser] CFT: Chromium 62 in meta-browser Raphael Kubo da Costa
2017-11-09 16:54 ` Otavio Salvador
2017-11-09 17:08   ` Raphael Kubo da Costa
2017-11-10 19:49 ` Trevor Woerner
2017-11-11  0:10   ` Ian Coolidge
2017-11-11 17:25     ` Otavio Salvador
2017-11-13 21:51       ` Ian Coolidge
2017-11-13 21:56         ` Ian Coolidge
2017-11-15 12:04 ` Raphael Kubo da Costa
2017-11-15 12:38   ` Martin Jansa
2017-11-15 14:20     ` Martin Jansa
2017-11-15 17:08     ` Raphael Kubo da Costa
2017-11-15 17:41       ` Martin Jansa [this message]
2017-11-15 17:49         ` Kubo Da Costa, Raphael
2017-11-15 19:34         ` Khem Raj
2017-11-23 10:22           ` Ayoub Zaki
2017-11-28  0:52             ` Ian Coolidge
2017-11-28  8:13               ` Ayoub Zaki
2017-11-28 11:58                 ` Otavio Salvador
2017-11-28 12:47                   ` Ayoub Zaki
2017-11-28 13:05                     ` Otavio Salvador
2017-11-28 21:44                       ` Ian Coolidge
2017-12-11 11:30             ` Raphael Kubo da Costa
2017-12-11 11:35               ` Ayoub Zaki

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=20171115174136.GA4530@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raphael.kubo.da.costa@intel.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.