Re: chromium detected as stripped

From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: "Andreas Müller" <schnitzeltony@googlemail.com>,
	"Raphael Kubo da Costa" <raphael.kubo.da.costa@intel.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: chromium detected as stripped
Date: Mon, 14 Aug 2017 16:43:52 -0300	[thread overview]
Message-ID: <CAP9ODKrwUkwdESj-qKrPjsKMN2=W-ZsYBb_+OYhbvrfgcoht2w@mail.gmail.com> (raw)
In-Reply-To: <CALbNGRT6v530xCdqLp3CRHKOtBZpg8JqYreOsUhFL5u-eV2O2A@mail.gmail.com>

Hello everyone,

On Mon, Aug 14, 2017 at 4:38 PM, Andreas Müller
<schnitzeltony@googlemail.com> wrote:
> On Mon, Aug 14, 2017 at 4:10 PM, Andreas Müller
> <schnitzeltony@googlemail.com> wrote:
>> On Mon, Aug 14, 2017 at 12:22 PM, Jussi Kukkonen
>> <jussi.kukkonen@intel.com> wrote:
>>>
>>>
>>> I chatted with rakuco who's done nice work with up to date chromium in
>>> meta-crosswalk, he's got some relevant commits related to this:
>>>
>>> https://github.com/rakuco/meta-crosswalk/commit/5aae1539c3d62b295dba40f494397c0797140b0f
>>> https://github.com/rakuco/meta-crosswalk/commit/c56aa2bf047d3a01e14f4f9bfe5f88664b333f36
>>>
>>> On a related note, this good work is currently a bit hidden in
>>> meta-crosswalk -- is there a chance we could get this combined with
>>> meta-browser (or whatever place makes sense)? I know next to nothing about
>>> chromium packaging so CCing Raphael and the meta-browser maintainers for
>>> comments.
>>>
>> That is interesting. If your suspicion is correct, we are very close
>> to the edge of file working properly or not. With meta-browser
>> c79cf6c7811afd2cd167e8967e3c29b1e797371e (16 commits behind master) I
>> get a proper detected and then split chromium. With meta-browser
>> master head file incorrectly reports that chrome is split already. I
>> did not check the exact size numbers but my file browser reports 4.3G
>> for both cases.
>>
>> Just to gather further information I think about bisecting meta-browser.
>>
> After first bisect build I checked size:: 4299018288 bytes / 2^32 is
> 4294967296 - so no need for further bisecting. Thanks Jussi for the
> hint.
>
> For now I'll choose old version - have not much time to take care.

Indeed it does sound like the proper workaround for now. That said,
I'd love to receive more help from meta-crosswalk people and avoid
duplication of work in packaging Chromium so I am adding Raphael on Cc
here so he can comment about how we can try to work together on this.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750