dev_install issues on ARM (libython error)

[Damien Nay]

So I was going to start poking around this shiny new HP 11 I received and I tried to execute dev_install and I got this error after it completed:

/usr/bin/python: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

It also threw me a 404 error for curl.  I seen another thread about dev_install errors so I also tried to set my binhost url with this command

sudo dev_install --reinstall -b https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R30-4537.147.0/packages

Since my chrome:version reads 

Google Chrome	30.0.1599.116 (Official Build 230306)
Platform	4537.147.0 (Official Build) stable-channel

If its any help I also tried this from the beta channel and it didnt work there either, althought that was before I tried using the -b argument.  Am I doing something wrong here or is this bug still in existence?  I did an ls on the python folder and it came up empty too...

[Mike Frysinger]

you probably forgot to use the - when using su

i.e. run `sudo su -`, not `sudo su`.

-mike

--
--
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
 

[Damien Nay]

Oh okay, I didnt realize I had to be logged in as root.  I thought it would run through sudo.  Can you explain how that works?  Or point me in the right direction?  Thanks!

--

-

Damien

[Mike Frysinger]

we added code to `dev_install` so it'll error out sooner rather than later when it detects a bad environment and issue a helpful message.  but it sounds like that isn't triggering in your case.  we might want to recheck the logic and see if it's still performing ...

https://chromium.googlesource.com/chromiumos/platform/dev-util/+/631fb3b10b392189a4ad3f017811d434220f6fed

-mike

[Damien Nay]

Ahh, it let me run all the way through it and didn't cry about anything until I tried to install the chromeos-dev package right after.

[Mike Frysinger]

ok, then that's properly to be expected atm.  i suspect doing `sudo emerge` will fail as you indicated.

this is because we have to seed the runtime env with a bunch of vars and those really only get loaded when you launch a root login shell (i.e. `sudo su -`).  this is to keep the env pollution down for the normal environment as only a developer would be launching a root login shell.  it's hard to say the same for many other operations -- they'll often be done in verified mode in which case we don't want this env pollution.

-mike