<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>2644</bug_id>
          
          <creation_ts>2012-06-21 18:31:09 +0000</creation_ts>
          <short_desc>Chromium Browser Integration</short_desc>
          <delta_ts>2013-04-29 11:55:13 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Other YP Layers</product>
          <component>layers</component>
          <version>1.3</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>(Scheduled)</status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>1.4.1</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Song Liu">song.liu</reporter>
          <assigned_to name="Laurentiu Palcu">laurentiu.palcu</assigned_to>
          <cc>alexandru.c.georgescu</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>otavio</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>sgw</cc>
    
    <cc>sstncr</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>22478</commentid>
    <comment_count>0</comment_count>
    <who name="Song Liu">song.liu</who>
    <bug_when>2012-06-21 18:31:09 +0000</bug_when>
    <thetext>There are some work already done for integrating the Chromium browser in Yocto. And we need to do more to complete this work and even improve it to be more usable for users. Specific issues we need to fix:

1. Create a new recipe or improve on the existing recipe to integrate Chromium browser.
2. make meta-chromium to compile on x-86 platforms.
3. fix host intrusion issues.

Acceptance Criteria:

1. Code is reasonably clean and readable.
2. Users can take the recipe and use it to integrate the Chromium browser in all Yocto core and meta-intel BSPs without any hacking.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>22557</commentid>
    <comment_count>1</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2012-06-25 18:14:22 +0000</bug_when>
    <thetext>Just to be clear, this should be done in a meta-chromian layer, not in oe-core, there is existing work for this.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>26163</commentid>
    <comment_count>2</comment_count>
    <who name="Otavio Salvador">otavio</who>
    <bug_when>2012-10-03 16:32:52 +0000</bug_when>
    <thetext>The meta-chromium has been merged onto meta-browser.

When working on this, please look at meta-browser to not duplicate work.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30471</commentid>
    <comment_count>3</comment_count>
    <who name="Otavio Salvador">otavio</who>
    <bug_when>2013-03-06 11:39:30 +0000</bug_when>
    <thetext>We had an upgrade of Chromium in meta-browser so please check if it is enough for your work or not.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30475</commentid>
    <comment_count>4</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-03-06 12:19:57 +0000</bug_when>
    <thetext>I built it successfully for qemux86 and atom-pc and it works just fine for both. However, I saw there&apos;s no support for x86-64 bit though... Is there a reason for that? Anyway, I just started building it for x86-64 and see what happens.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30482</commentid>
    <comment_count>5</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-03-07 07:55:07 +0000</bug_when>
    <thetext>I succeeded to run chromium in qemux86-64 too, after some slight changes to the chromium recipe and adding the gypi config for ia64 architecture.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30599</commentid>
    <comment_count>6</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-03-11 08:49:32 +0000</bug_when>
    <thetext>Chromium was compiled and tested on x86 and x86-64 successfully. We can close this now.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30702</commentid>
    <comment_count>7</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2013-03-14 11:46:22 +0000</bug_when>
    <thetext>Currently I am trying to verify this on x86_64 qemu machine, but I encountered some errors.
Will close the feature after the problems are resolved.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30703</commentid>
    <comment_count>8</comment_count>
    <who name="Otavio Salvador">otavio</who>
    <bug_when>2013-03-14 11:47:44 +0000</bug_when>
    <thetext>Are you looking at it?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30704</commentid>
    <comment_count>9</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-03-14 12:15:16 +0000</bug_when>
    <thetext>(In reply to comment #7)
&gt; Currently I am trying to verify this on x86_64 qemu machine, but I
&gt; encountered some errors.
&gt; Will close the feature after the problems are resolved.

Would you please tell what the errors are? Also, attach the relevant logs.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30707</commentid>
    <comment_count>10</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-03-14 13:12:02 +0000</bug_when>
    <thetext>FYI, I just built a core-image-sato from scratch using latest oe-core, meta-oe and meta-browser layers without issues. Also, chrome starts just fine.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30735</commentid>
    <comment_count>11</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-03-15 09:30:00 +0000</bug_when>
    <thetext>Chromium builds and runs just fine on x86-64. If you reopen it, for some reason, please provide more info about the problem.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30736</commentid>
    <comment_count>12</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2013-03-15 09:32:26 +0000</bug_when>
    <thetext>I don&apos;t know why this was reopened. I just commented that I am verifying this.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30753</commentid>
    <comment_count>13</comment_count>
    <who name="Otavio Salvador">otavio</who>
    <bug_when>2013-03-15 11:12:17 +0000</bug_when>
    <thetext>(In reply to comment #12)
&gt; I don&apos;t know why this was reopened. I just commented that I am verifying
&gt; this.

I did the reopen as you said it failed for you so please give it a try.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30959</commentid>
    <comment_count>14</comment_count>
      <attachid>1128</attachid>
    <who name="Stefan Stanacar">sstncr</who>
    <bug_when>2013-03-21 13:06:15 +0000</bug_when>
    <thetext>Created attachment 1128
log.do_rootfs</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30960</commentid>
    <comment_count>15</comment_count>
    <who name="Stefan Stanacar">sstncr</who>
    <bug_when>2013-03-21 13:08:58 +0000</bug_when>
    <thetext>Build Configuration:
BB_VERSION        = &quot;1.17.1&quot;
BUILD_SYS         = &quot;x86_64-linux&quot;
NATIVELSBSTRING   = &quot;Fedora-18&quot;
TARGET_SYS        = &quot;x86_64-poky-linux&quot;
MACHINE           = &quot;qemux86-64&quot;
DISTRO            = &quot;poky&quot;
DISTRO_VERSION    = &quot;1.3+snapshot-20130321&quot;
TUNE_FEATURES     = &quot;m64&quot;
TARGET_FPU        = &quot;&quot;
meta              
meta-yocto        
meta-yocto-bsp    = &quot;master:9ffee9add2d0380f4025e7a678a166f25a7d659e&quot;
meta-oe           
meta-gnome        = &quot;master:e075421a12a62f12294bf44e13deeca0594d5549&quot;
meta-browser      = &quot;master:359cdae903c3772796b4658dd3129742d9a76d05&quot;


Using the above commits and MACHINE I can bitbake chromium successfully however when doing IMAGE_INSTALL_append = &quot; chromium&quot;, core-image-sato fails at do_rootfs:


Computing transaction...error: Can&apos;t install nspr-4.9.5-r1@x86_64: no package provides /usr/bin/perl

Log attached (previous comment.)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>30962</commentid>
    <comment_count>16</comment_count>
    <who name="Stefan Stanacar">sstncr</who>
    <bug_when>2013-03-21 13:23:38 +0000</bug_when>
    <thetext>One more thing: chromium doesn&apos;t build if the host system doesn&apos;t have a Digest-MD5 perl module installed. I have two systems where compile failed because I didn&apos;t have perl-Digest-MD5 installed (this is the fedora package name, differs on others). This is something specific to the chromium build system (ninja) I assume.
Installing it solves the problem but I have to wonder if is it okay to assume the users will have the module installed. No other poky/oe-core/meta-oe build required me to install extra packages other than what&apos;s  specified in the Yocto Quick Start. One solution is to use the sanity tests and check for the module and let the user know what&apos;s required before starting the build.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>31098</commentid>
    <comment_count>17</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-03-25 10:35:44 +0000</bug_when>
    <thetext>(In reply to comment #15)
&gt; Build Configuration:
&gt; BB_VERSION        = &quot;1.17.1&quot;
&gt; BUILD_SYS         = &quot;x86_64-linux&quot;
&gt; NATIVELSBSTRING   = &quot;Fedora-18&quot;
&gt; TARGET_SYS        = &quot;x86_64-poky-linux&quot;
&gt; MACHINE           = &quot;qemux86-64&quot;
&gt; DISTRO            = &quot;poky&quot;
&gt; DISTRO_VERSION    = &quot;1.3+snapshot-20130321&quot;
&gt; TUNE_FEATURES     = &quot;m64&quot;
&gt; TARGET_FPU        = &quot;&quot;
&gt; meta              
&gt; meta-yocto        
&gt; meta-yocto-bsp    = &quot;master:9ffee9add2d0380f4025e7a678a166f25a7d659e&quot;
&gt; meta-oe           
&gt; meta-gnome        = &quot;master:e075421a12a62f12294bf44e13deeca0594d5549&quot;
&gt; meta-browser      = &quot;master:359cdae903c3772796b4658dd3129742d9a76d05&quot;
&gt; 
&gt; 
&gt; Using the above commits and MACHINE I can bitbake chromium successfully
&gt; however when doing IMAGE_INSTALL_append = &quot; chromium&quot;, core-image-sato fails
&gt; at do_rootfs:
&gt; 
&gt; 
&gt; Computing transaction...error: Can&apos;t install nspr-4.9.5-r1@x86_64: no
&gt; package provides /usr/bin/perl
&gt; 
&gt; Log attached (previous comment.)

It turns out this happens only when RPM backend is used for the package manager. It works just fine with opkg... I&apos;ll have a look.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32646</commentid>
    <comment_count>18</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2013-04-25 15:12:03 +0000</bug_when>
    <thetext>Looks like a missing dependency on perl in the nspr package,</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32690</commentid>
    <comment_count>19</comment_count>
    <who name="Saul Wold">sgw</who>
    <bug_when>2013-04-26 21:12:18 +0000</bug_when>
    <thetext>This seems very strange, I have reviewed the recipe and code, the -dev package has a dependency on perl, for the runtests.pl script, the meta-browser layer has a recipe for NSS, which does have a reference to perl in the smime_nss perl script.  The reference is incorrect as it points to /usr/local/bin/perl, this should be fixed to #!/usr/bin/env perl

Similar to this:

	sed -i -e &apos;1s,#!.*perl,#! ${USRBINPATH}/env perl,&apos; smime</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32696</commentid>
    <comment_count>20</comment_count>
    <who name="Otavio Salvador">otavio</who>
    <bug_when>2013-04-27 14:53:52 +0000</bug_when>
    <thetext>(In reply to comment #19)
&gt; This seems very strange, I have reviewed the recipe and code, the -dev
&gt; package has a dependency on perl, for the runtests.pl script, the
&gt; meta-browser layer has a recipe for NSS, which does have a reference to perl
&gt; in the smime_nss perl script.  The reference is incorrect as it points to
&gt; /usr/local/bin/perl, this should be fixed to #!/usr/bin/env perl
&gt; 
&gt; Similar to this:
&gt; 
&gt; 	sed -i -e &apos;1s,#!.*perl,#! ${USRBINPATH}/env perl,&apos; smime

Saul, are you going to propose a patch for this fix?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32703</commentid>
    <comment_count>21</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2013-04-29 06:49:11 +0000</bug_when>
    <thetext>(In reply to comment #20)
&gt; (In reply to comment #19)
&gt; &gt; This seems very strange, I have reviewed the recipe and code, the -dev
&gt; &gt; package has a dependency on perl, for the runtests.pl script, the
&gt; &gt; meta-browser layer has a recipe for NSS, which does have a reference to perl
&gt; &gt; in the smime_nss perl script.  The reference is incorrect as it points to
&gt; &gt; /usr/local/bin/perl, this should be fixed to #!/usr/bin/env perl
&gt; &gt; 
&gt; &gt; Similar to this:
&gt; &gt; 
&gt; &gt; 	sed -i -e &apos;1s,#!.*perl,#! ${USRBINPATH}/env perl,&apos; smime
&gt; 
&gt; Saul, are you going to propose a patch for this fix?

Otavio,

I sent a patch for this a long time ago:
http://lists.linuxtogo.org/pipermail/openembedded-devel/2013-March/044575.html

But it was never merged to meta-browser... Unfortunately I was busy working on other things and I didn&apos;t follow what happened with it. So, the patch fixing this is out there.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>32709</commentid>
    <comment_count>22</comment_count>
    <who name="Otavio Salvador">otavio</who>
    <bug_when>2013-04-29 11:55:13 +0000</bug_when>
    <thetext>Merged: https://github.com/OSSystems/meta-browser/commit/42c0fc5a37de640a4036d80ca0ebb89882a8fb01</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>1128</attachid>
            <date>2013-03-21 13:06:15 +0000</date>
            <delta_ts>2013-03-21 13:06:15 +0000</delta_ts>
            <desc>log.do_rootfs</desc>
            <filename>log.do_rootfs.25218</filename>
            <type>application/octet-stream</type>
            <size>1583</size>
            <attacher name="Stefan Stanacar">sstncr</attacher>
            
              <data encoding="base64">REVCVUc6IEV4ZWN1dGluZyBzaGVsbCBmdW5jdGlvbiBkb19yb290ZnMKUHJldmlvdXMgcmVwbyBm
aWxlIG1pc3Npbmc6IC9ob21lL3N0ZWZhbnMveW9jdG8vYnVpbGRzL2Nocm9taXVtL3RtcC9kZXBs
b3kvcnBtL2FsbC9yZXBvZGF0YS9wcmltYXJ5LnhtbC5negpQcmV2aW91cyByZXBvIGZpbGUgbWlz
c2luZzogL2hvbWUvc3RlZmFucy95b2N0by9idWlsZHMvY2hyb21pdW0vdG1wL2RlcGxveS9ycG0v
cWVtdXg4Nl82NC9yZXBvZGF0YS9wcmltYXJ5LnhtbC5negpQcmV2aW91cyByZXBvIGZpbGUgbWlz
c2luZzogL2hvbWUvc3RlZmFucy95b2N0by9idWlsZHMvY2hyb21pdW0vdG1wL2RlcGxveS9ycG0v
eDg2XzY0L3JlcG9kYXRhL3ByaW1hcnkueG1sLmd6Ck5vdGU6IGNvbmZpZ3VyaW5nIFJQTSBwbGF0
Zm9ybSBzZXR0aW5ncwpOb3RlOiBjb25maWd1cmluZyBSUE0gc3lzdGVtIHByb3ZpZGVzCk5vdGU6
IGNvbmZpZ3VyaW5nIFJQTSBEQiBzZXR0aW5ncwpOb3RlOiBjb25maWd1cmluZyBTbWFydCBzZXR0
aW5ncwoKCgoKCgpOb3RlOiBhZGRpbmcgU21hcnQgY2hhbm5lbCBxZW11eDg2XzY0ICgzMCkKCgpO
b3RlOiBhZGRpbmcgU21hcnQgY2hhbm5lbCB4ODZfNjQgKDI1KQoKCk5vdGU6IGFkZGluZyBTbWFy
dCBjaGFubmVsIGFsbCAoMTApCgoKTm90ZTogY29uZmlndXJpbmcgUlBNIGNyb3NzLWluc3RhbGwg
c2NyaXB0bGV0X3dyYXBwZXIKClVwZGF0aW5nIGNhY2hlLi4uICAgICAgICAgICAgICAgIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyBbMTAwJV0KClNhdmluZyBjYWNoZS4u
LgoKTm90ZTogYWRkaW5nIFNtYXJ0IFJQTSBEQiBjaGFubmVsCgpOb3RlOiB0byBiZSBpbnN0YWxs
ZWQ6ICBwYWNrYWdlZ3JvdXAtY29yZS1zc2gtZHJvcGJlYXJAYWxsIHBhY2thZ2Vncm91cC1jb3Jl
LXgxMS1zYXRvLWdhbWVzQHFlbXV4ODZfNjQgcGFja2FnZWdyb3VwLWNvcmUteDExLWJhc2VAYWxs
IHNtYXJ0cG1AeDg2XzY0IHBzcGxhc2hAeDg2XzY0IHBhY2thZ2Vncm91cC1jb3JlLWJvb3RAcWVt
dXg4Nl82NCBjaHJvbWl1bUB4ODZfNjQgcGFja2FnZWdyb3VwLWJhc2UtZXh0ZW5kZWRAcWVtdXg4
Nl82NCBycG1AeDg2XzY0IHBhY2thZ2Vncm91cC1jb3JlLXgxMS1zYXRvQHFlbXV4ODZfNjQgbG9j
YWxlLWJhc2UtZW4tdXNAeDg2XzY0IGxvY2FsZS1iYXNlLWVuLWdiQHg4Nl82NApMb2FkaW5nIGNh
Y2hlLi4uClVwZGF0aW5nIGNhY2hlLi4uICAgICAgICAgICAgICAgIyMjIyMjIyMjIyMjIyMjIyMj
IyMjIyMjIyMjIyMjIyMjIyMjIyMjIyBbMTAwJV0KCkNvbXB1dGluZyB0cmFuc2FjdGlvbi4uLmVy
cm9yOiBDYW4ndCBpbnN0YWxsIG5zcHItNC45LjUtcjFAeDg2XzY0OiBubyBwYWNrYWdlIHByb3Zp
ZGVzIC91c3IvYmluL3BlcmwKClNhdmluZyBjYWNoZS4uLgoKRVJST1I6IEZ1bmN0aW9uIGZhaWxl
ZDogZG9fcm9vdGZzIChzZWUgL2hvbWUvc3RlZmFucy95b2N0by9idWlsZHMvY2hyb21pdW0vdG1w
L3dvcmsvcWVtdXg4Nl82NC1wb2t5LWxpbnV4L2NvcmUtaW1hZ2Utc2F0by8xLjAtcjAvdGVtcC9s
b2cuZG9fcm9vdGZzLjI1MjE4IGZvciBmdXJ0aGVyIGluZm9ybWF0aW9uKQo=
</data>

          </attachment>
      

    </bug>

</bugzilla>