install-build-deps.sh doesn't work

[Dmitry Oleshko]

Hello folks!

I'm trying to understand what I'm doing wrong.

I've followed the instructions (http://dev.chromium.org/developers/how-tos/get-the-code), but running of "gclient runhooks" keeps annoying me with one or another missed package.

So i have to install them manually one by one after regular repeat of "runhooks".

Could anyone please clarify what should be done in order to make install-build-deps.sh done its job completely?

Thanks!

[Nico Weber]

Did you run build/install-build-deps.sh? What was the output of that step?

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Dmitry Oleshko]

Hi Nico!

yep I did it
and the final output is:

It produces the following output:

Reading package lists... Done

Building dependency tree       

Reading state information... Done

E: Unable to locate package lib32ncurses5-dev

E: Unable to locate package lib32z1-dev

You will have to install the above packages yourself.

But it seems to be OK since I have an x64 Ubuntu. And I've installed x64 versions of those packages manually. 

[Nico Weber]

Huh!

What does runhooks complain about in particular?

Which version of Ubuntu are you using? The script probably works best on trusty these days.

[Dmitry Oleshko]

Hi Nico,

I don't remember the messages, but I have a list of packages I had to install: 

• bison libnss3-dev libpulse-dev libgtk2.0-dev libxtst-dev xorg-dev libudev-dev libgconf2-dev libgnome-keyring-dev libpci-dev libcups2-dev libexif-dev gperf libcap-dev libasound2-dev libdrm-dev libssl-dev
  

I'm using Ubuntu 14.10:

[Primiano Tucci]

Your screenshot seems to suggest that you are NOT using a 64-bit OS.

This is not supported, as indicated by our docs (https://code.google.com/p/chromium/wiki/LinuxBuildInstructions).

Even if you manage to succeed with with the deps install, it is very likely that you will have a hard time linking.

[santosh mahto]

Hi 

Few months back I  did set up for ubuntu14.10 and using it now. That time I also

enabled it to work in ubuntu14.10. So I guess it is due to your own  local problem.

Best thing you can try to do setup inside chroot :

 https://src.chromium.org/svn/trunk/src/build/install-chroot.sh   

Just follow the instruction.

Does your "sudo apt-get update" works fine? 

and Could you check options ticked in  System settings->Software updates->software ?

Regards

Santosh Mahto

sam...@cisco.com

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Dmitry Oleshko]

Hi All

yep,  I was a mistake with x64 and I thought, that packages without "32" in names were for 64-bit OS.
But anyway, system had taken what it needed and build has completed successfully.

Yes, "sudo apt-get update" works fine.

Concerning update settings:

 

So again, my question was: if it is known what packages should be installed to OS for content-shell successful build - why they are not included to install-build-deps.sh? 

I've faced the same issue a year before, when I tried BLINK for the first time. I just hoped that such trivial issues should have been fixed already...

[Marc-Antoine Ruel]

The vast majority of Chromium developers use the LTS version. When you use a non-LTS version, you may hit more issues.

M-A