Re: [Chrome OS] Can't find libjpeg.so.8 when building ChromeOS test image on R19 ToT

[Gaurav Shah]

-team, +cros-dev

On Thu, May 10, 2012 at 1:07 PM, Xiaohan Wang (王消寒) <xhw...@google.com> wrote:
> Hello,
>
> I have two follow-up questions:
>
> After I do "repo sync", how do I know which revision of chrome I am at?
> Is there a way to cherry-pick a chrome CL manually if it's not yet in the
> chromeos-chrome repository I synced to?
>
> Best,
> Xiaohan
>
> On Thu, May 10, 2012 at 1:01 AM, Xiaohan Wang (王消寒) <xhw...@google.com>
> wrote:
>>
>> Commenting out ">=media-libs/jpeg-7" then "emerge-x86-alex jpeg" fixed the
>> issue.
>>
>> I also tried not to use my own chrome checkout and got the same error.
>> Sounds like some mismatch with clang/asan built chromeos-chrome. Should I
>> file a bug on this?
>>
>> On Wed, May 9, 2012 at 4:33 PM, Xiaohan Wang (王消寒) <xhw...@google.com>
>> wrote:
>>>
>>> I cleaned my build folder and am trying again. Will let you know what I
>>> get later. Thanks!
>>>
>>>
>>> On Wed, May 9, 2012 at 4:26 PM, Richard Barnette <jrbar...@google.com>
>>> wrote:
>>>>
>>>> On May 9, 2012, at 4:25 PM, Mike Frysinger wrote:
>>>>
>>>> > edit chromiumos-overlay/profiles/targets/chromeos/package.mask and
>>>> > remove the line Richard mentioned:
>>>> >> =media-libs/jpeg-7
>>>> > -mike
>>>> >
>>>> I already gave that advice offline, but it hasn't worked for him.
>>>>
>>>> Xiaohan, can you post your latest error messages?
>>>>
>>>>
>>>>
>>>> > On Wed, May 9, 2012 at 7:23 PM, Xiaohan Wang (王消寒) <xhw...@google.com>
>>>> > wrote:
>>>> >> Thanks Mike and Richard,
>>>> >>
>>>> >> I tried "emerge-x86-alex jpeg" and it's still giving me the same jpeg
>>>> >> 6 lib.
>>>> >>
>>>> >> So how do I make sure my chrome checkout matches my cros checkout?
>>>> >> Now I
>>>> >> have a R19 chromeos checkout and a M19 chrome checkout, I use
>>>> >> "cros_sdk
>>>> >> --enter --chrome_root=/hdd2/xhwang/chrome/" to point to my chrome
>>>> >> source. I
>>>> >> thought by keeping both ToT would be okay, but apparently I was
>>>> >> wrong.
>>>> >>
>>>> >> Xiaohan
>>>> >>
>>>> >> On Wed, May 9, 2012 at 3:04 PM, Mike Frysinger <vap...@google.com>
>>>> >> wrote:
>>>> >>>
>>>> >>> the image you're creating needs to match the system that the chrome
>>>> >>> was built against. it seems your image has an old libjpeg (probably
>>>> >>> .so.6) but you compiled against a system that contains a new libjpeg
>>>> >>> (.so.8 according to the error message). try doing:
>>>> >>> emerge-x86-alex jpeg
>>>> >>> and make sure it installs version 8+
>>>> >>> -mike
>>>> >>>
>>>> >>> On Wed, May 9, 2012 at 5:47 PM, Xiaohan Wang <xhw...@google.com>
>>>> >>> wrote:
>>>> >>>> I am building my own test image using ToT R19 branch as well as my
>>>> >>>> own
>>>> >>>> chromeos-chrome with clang/asan using ToT m19 branch.
>>>> >>>> chromeos-chome
>>>> >>>> builds
>>>> >>>> fine. Now when I build test-image, I got this error:
>>>> >>>>
>>>> >>>> Problem with
>>>> >>>>
>>>> >>>>
>>>> >>>> /home/xhwang/trunk/src/build/images/x86-alex/R19-2046.84.2012_05_09_1335-a1/rootfs/opt/google/chrome/chrome:
>>>> >>>> Can't find libjpeg.so.8
>>>> >>>> ERROR : test_image_content: Failed dependency check
>>>> >>>> An error occurred in your build so your latest output directory is
>>>> >>>> invalid.
>>>> >>>>
>>>> >>>> I checked that I do have libjpeg.so.8 in /usr/lib64/ in chroot.
>>>> >>>> Does
>>>> >>>> anybody
>>>> >>>> know what might cause this? I am so close to have the test image
>>>> >>>> built...
>>>> >>
>>>> >>
>>>> >
>>>> > --
>>>> > You received this message because you are subscribed to the Google
>>>> > Groups "Chrome OS-team" group.
>>>> > To post to this group, send email to chrome...@google.com
>>>> > To unsubscribe from this group, send email to
>>>> > chromeos-tea...@google.com
>>>> > For more options, visit this group at
>>>> > http://groups.google.com/a/google.com/group/chromeos-team?hl=en
>>>> > For more information about Google Chrome OS please visit:
>>>> > http://go/chromeos
>>>>
>>>> -- jrb
>>>> Ever tried. Ever failed. No matter. Try again. Fail again. Fail better.
>>>> Samuel Beckett - "Worstward Ho"
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Chrome OS-team" group.
> To post to this group, send email to chrome...@google.com
> To unsubscribe from this group, send email to
> chromeos-tea...@google.com
> For more options, visit this group at
> http://groups.google.com/a/google.com/group/chromeos-team?hl=en
> For more information about Google Chrome OS please visit: http://go/chromeos



--
-g

[Mike Frysinger]

hmm, i recall there being a bug recently wrt clang and sysroots. it'd
wrongly pick up stuff in / when it should have been picking up stuff
in the target sysroot. you're probably hitting that.
-mike

[David Moore]

Was this ever resolved? More to the point is it possible to build an asan version of chrome either in or out of the chroot and run it on the device? I'm trying to track down a random crasher.

Dave

--

Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Denis Glotov]

Hi!

Yes, building Chrome with Clang and ASAN under chroot is possible and working. The buildbot went green yesterday: http://build.chromium.org/p/chromiumos/builders/x86%20generic%20ASAN

I updated the instruction at https://sites.google.com/a/chromium.org/dev/chromium-os/how-tos-and-troubleshooting/llvm-clang-build.

On Wed, May 16, 2012 at 9:09 PM, Xiaohan Wang (王消寒) <xhw...@google.com> wrote:

+chrome...@google.com as I can't post to chromium-os-dev@ for some reason.

Also I am wondering where's the best place to share these steps with more people.

1. I was just following Chromium OS developer guide: http://dev.chromium.org/chromium-os/developer-guide. After build_packages and before build_image step, do:
   export CC="clang" CXX="clang++" && export USE="clang asan" && emerge-$BOARD chromeos-chrome
2. This will build chromeos-chrome with asan. The built binary file is located at (in chroot):
   /var/cache/chromeos-chrome/chrome-src/src/out_x86-alex/Release/chrome You want to keep it somewhere convenient because you'll need it to get symbols when you get an asan log. To double check if you have asan built in, try "nm -C chrome | grep asan" to see if you have asan symbols.
3. Then follow normal build step and try it on your chromeos device.
4. After you run what ever you need to run, either with a crash or not, you can check /var/log/ui/ui.LATEST to see if you have any  asan logs. 
5. If you see any asan logs, copy them over to your Linux machine. Then run:
1. Copy the chrome binary (from step 2) with symbols somewhere to your linux box. 
2. In the log file replace "/opt/google/chrome/chrome" with the new path. 
3. run "chrome/src/third_party/asan/scripts/asan_symbolize.py < log  | c++filt" 

Xiaohan

On Wed, May 16, 2012 at 9:00 AM, Xiaohan Wang (王消寒) <xhw...@google.com> wrote:

Yes. I just build asan chromeos-chrome last week. I'll share the steps with you later today.

On Wed, May 16, 2012 at 8:56 AM, David Moore <dave...@google.com> wrote:

Was this ever resolved? More to the point is it possible to build an asan version of chrome either in or out of the chroot and run it on the device? I'm trying to track down a random crasher.

Dave

On Thu, May 10, 2012 at 1:15 PM, Mike Frysinger <vap...@chromium.org> wrote:

--

Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

--
Thank you,
Denis