USE="component_build" for chromeos build is broken when installing |
||||||||
Issue description
When building chrome with component_build, I cannot make chromeos image
Step
1. build chrome image
2. USE="component_build clang" CHROME_ORIGIN=LOCAL_SOURCE emerge-${BOARD} chromeos-chrome
3. ./build_image --board=${BOARD} --noenable_rootfs_verification test
It fails because chrome ebuild doesn't know how to install so files.
Error log:
/mnt/host/source/src/scripts/build_library/test_image_content.sh: line 41: echo: write error: Broken pipe
ERROR : test_elf_deps: Failed dependency check
ERROR : Package: chromeos-base/chromeos-chrome-59.0.3070.0_rc-r1
ERROR : /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/opt/google/chrome/libnet_with_v8.so (interpreter => None)
ERROR : libpthread.so.0 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libpthread.so.0
ERROR : ld-linux-x86-64.so.2 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/ld-linux-x86-64.so.2
ERROR : libnet.so => None
ERROR : libbase.so => None
ERROR : libgin.so => None
ERROR : liburl.so => None
ERROR : libv8.so => None
ERROR : libstdc++.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/usr/lib64/libstdc++.so.6
ERROR : libm.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libm.so.6
ERROR : libgcc_s.so.1 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/usr/lib64/libgcc_s.so.1
ERROR : libc.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libc.so.6
ERROR : Package: chromeos-base/chromeos-chrome-59.0.3070.0_rc-r1
ERROR : /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/opt/google/chrome/libmojo_system_impl.so (interpreter => None)
ERROR : libpthread.so.0 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libpthread.so.0
ERROR : ld-linux-x86-64.so.2 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/ld-linux-x86-64.so.2
ERROR : libmojo_public_system.so => None
ERROR : libbase.so => None
ERROR : libcrcrypto.so => None
ERROR : libstdc++.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/usr/lib64/libstdc++.so.6
ERROR : libm.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libm.so.6
ERROR : libgcc_s.so.1 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/usr/lib64/libgcc_s.so.1
ERROR : libc.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libc.so.6
ERROR : Package: chromeos-base/chromeos-chrome-59.0.3070.0_rc-r1
ERROR : /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/opt/google/chrome/libpresenter.so (interpreter => None)
ERROR : libpthread.so.0 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libpthread.so.0
ERROR : ld-linux-x86-64.so.2 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/ld-linux-x86-64.so.2
ERROR : libbase.so => None
ERROR : libbindings.so => None
ERROR : libapp_list.so => None
ERROR : libaura.so => None
ERROR : libcompositor.so => None
ERROR : libgeometry.so => None
ERROR : libviews.so => None
ERROR : libmojo_public_system_cpp.so => None
ERROR : libmojo_public_system.so => None
ERROR : libipc.so => None
ERROR : libgpu.so => None
ERROR : libgfx.so => None
ERROR : libcolor_space.so => None
ERROR : libskia.so => None
ERROR : libui_base.so => None
ERROR : libevents_base.so => None
ERROR : libdisplay_types.so => None
ERROR : libdisplay.so => None
ERROR : libgfx_ipc_color.so => None
ERROR : libcc.so => None
ERROR : libcc_base.so => None
ERROR : libevents.so => None
ERROR : libui_base_ime.so => None
ERROR : libstdc++.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/usr/lib64/libstdc++.so.6
ERROR : libgcc_s.so.1 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/usr/lib64/libgcc_s.so.1
ERROR : libm.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libm.so.6
ERROR : libc.so.6 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libc.so.6
ERROR : Package: chromeos-base/chromeos-chrome-59.0.3070.0_rc-r1
ERROR : /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/opt/google/chrome/libui_chromeos.so (interpreter => None)
ERROR : libpthread.so.0 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/libpthread.so.0
ERROR : ld-linux-x86-64.so.2 => /mnt/host/source/src/build/images/samus/R60-9471.0.2017_04_19_1001-a1/rootfs/lib64/ld-linux-x86-64.so.2
ERROR : libbase.so => None
ERROR : libchromeos.so => None
ERROR : libaura.so => None
,
Apr 19 2017
This is not a toolchain issue. Changing label to "build". cc'ing stevenjb. Last time we saw references to component_build was at the GN migration time. I don't remember it it was working at that time. Steve, do you remember anything about this? also, why are you doing component_build?
,
Apr 19 2017
This is not well supported and may have broken during the GN migration. In theory we support it here: https://cs.corp.google.com/chromeos_public/chromite/lib/chrome_util.py?q=component_build+file:%5Echromite/+package:%5Echromeos_public$&l=375 Maybe test_image_content.sh needs to be updated? (I don't know anything about that script). What is the use case?
,
Apr 19 2017
i doubt test_image_content.sh is the problem. if the files aren't installed or are missing proper linking, then we consider the image to be broken.
,
Apr 20 2017
Hm, not sure why I was Cc-ed, I don't have a clue about this issue. @dongseong.hwang -- if you need my input, please add me again and ask your question directly. Thanks!
,
Mar 14 2018
This bug is Untriaged and very old. Because it has an owner, the status will be set to assigned to avoid closing a bug someone is using. If this bug still needs triage, change it back to Untriaged.
,
Mar 30 2018
,
Mar 30 2018
,
Jun 29 2018
Is this still happening? Over to the Build team.
,
Jun 29 2018
component builds are handled by deploy_chrome in chromite. from the build team side, i don't think component builds are a priority. i'd leave it to Steven/Achuith to decide priority here. i'm assuming component builds are also broken for Simple Chrome.
,
Jun 29 2018
As mentioned in comment #3, this isn't something that I think the team should prioritize supporting (even if we had staffing to do so). There is a long list of other chrome on chromeos build improvements that would likely benefit more developers :) (See Hotlist-CrOS-Gardener if you're curious, although the list hasn't been triaged in a while). That said, if a developer using this workflow feels strongly enough to test this and make any changes required, I would be happy to review any such changes and help make sure we can support component builds in a maintainable way. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by dongseon...@intel.com
, Apr 19 2017