dev_install failed on Samsung ARM chromebook

[m0g]

Hello,

I hope this message belongs here.

I'm trying this guide for having access to emerge on chromeos.

http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/install-software-on-base-images

Unfortunately I always got the same error which is

$ sudo dev_install 
Starting installation of developer packages. First, we download the necessary files. Downloading https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/full-3.168.0.0/packages/app-misc/mime-types-8.tbz2 
 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 
100 127 100 127 0 0 252 0 --:--:-- --:--:-- --:--:-- 305 
[: 184: -ne: unexpected operator Extracting /usr/local/portage/packages/app-misc/mime-types-8.tbz2

I think that it somehow returns a 404 everytime. Thanks for your help

[Chris Sosa]

There are a few bugs that have this functionality currently broken:

http://code.google.com/p/chromium-os/issues/list?q=label%3Adev_install

To get around your issue you need to specify a binhost.

What version are you using? URL: "about:version" -- CHROMEOS_RELEASE_VERSION

Your dev-installer prebuilts would be at:

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R23-<version>/packages

So specify it with --binhost

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

[m0g]

Thanks for the answer.

So I managed to properly launch the script. Even if one can find an error in line 122 (replace cur_exit_code=$? per curl_exit_code=$?). But I still end up with a bug when trying to emerge chromeos-dev:

Files downloaded, configuring emerge.
Emerge installation complete. Installing additional optional packages.
Install chromeos-dev package now (y/n)?y
/usr/bin/python: error while loading shared libraries: libpython2.6.so.1.0: cannot open shared object file: No such file
or directory

[John Pribula]

I have tried these work around's and I'm still receiving this error.

[Chris Sosa]

It looks like python might be looking for its libraries in the wrong place -- should be in /usr/local/lib not /usr/lib. Are you running from VT2 or the crosh shell? I'll take a look when I get a chance

-Sosa

[Chris Sosa]

So worked for me outside the other outstanding bugs. I'm guessing you didn't either "sudo su -" or didn't specify the --binhost correctly. If you send me your logs I can tell you which of the two it is.  Feel free to star the bugs listed on the help page as well for updates.

I just installed gmerge and qemacs fine on my samsung device which is running from the beta-channel.

[Jeremiah Dow]

I just had the same issue on the Samsung series 5 550 (lumpy R21-2465.228).

The problem was the libraries for python and the rest or the packages were being extracted to lib64 rather than lib as the script was expecting.

m0g - try resetting this environment variable and you should be able to run python / emerge

export LD_LIBRARY_PATH="/usr/local/lib64"

[Mike Frysinger]

ARM uses "lib", not "lib64"

-mike

[Steven Stallion]

On Thursday, November 15, 2012 11:24:10 AM UTC-8, Chris Sosa wrote:

So worked for me outside the other outstanding bugs. I'm guessing you didn't either "sudo su -" or didn't specify the --binhost correctly. If you send me your logs I can tell you which of the two it is.  Feel free to star the bugs listed on the help page as well for updates.

I just installed gmerge and qemacs fine on my samsung device which is running from the beta-channel.

Has anyone been able to emerge chromeos-dev after a successful dev_install? I've tried both latest stable and dev channel releases to no avail. I've had zero problems with dev_install apart from specifying the appropriate binhost. I'm able to emerge other packages (ie. gmerge) that don't have a dependency on glibc.

localhost ~ # emerge chromeos-dev

!!! PORTAGE_BINHOST unset, but use is requested.

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy ">=sys-libs/glibc-2.10" for /usr/local/.

(dependency required by "sys-fs/udev-171-r2" [binary])

(dependency required by "chromeos-base/flimflam-0.0.1-r519" [binary])

(dependency required by "chromeos-base/flimflam-test-0.0.1-r385" [binary])

(dependency required by "chromeos-base/chromeos-dev-0.1.0-r57" [binary])

(dependency required by "chromeos-dev" [argument])

Cheers,

Steve

[Chris Sosa]

It's just a bug.

You can source /etc/profile in any shell to get it working correctly.
I have a fix for M26 that resolves this issue.

On Sat, Jan 12, 2013 at 3:28 PM, Isaac Xin Pei <isaa...@gmail.com> wrote:
>
> hello,
>
> I just followed the instruction and got the dev_install works on my sumsung
> arm chromebook. a related question is:
>
> I am a newbie on chromebook: why normal user can not access python?
> if I do sudo su -; then python can be invoked properly, but
>
> : chronos@localhost ~ $ python

> python: error while loading shared libraries: libpython2.6.so.1.0: cannot
> open shared object file: No such file or directory
>

> chronos@localhost ~/Workbench $ python

> python: error while loading shared libraries: libpython2.6.so.1.0: cannot
> open shared object file: No such file or directory
>
>
>
>

> is it a user privilege issue or some others? I would like to have access to
> python ...
>
> Thanks!

>
>
> On Thursday, November 15, 2012 11:24:10 AM UTC-8, Chris Sosa wrote:
>>

[Anand Patil]

Hi all,

I've been trying to follow this thread but haven't had any luck on my Samsung ARM chromebook. It would be great if someone could make the steps more explicit. I would love to be able to emerge Linux packages on my chromebook before the official fix comes around, and this thread is the most topical I can find, but it isn't quite clear enough for me to follow it.

For example, I've tried to follow Chris's instructions to get around the initial 404 bug:

> To get around your issue you need to specify a binhost.

> 

> What version are you using? URL: "about:version" -- CHROMEOS_RELEASE_VERSION

> 

> Your dev-installer prebuilts would be at:

> 

> https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R23-<version>/packages

> 

> So specify it with --binhost

When I go to about:version, I don't see CHROMEOS_RELEASE_VERSION anywhere on the page. I see: 

Google Chrome	23.0.1271.99 (Official Build 172193)
Platform	2913.260.0 (Official Build) stable-channel daisy

followed by other things. (Note, I told my chromebook to update to 'dev channel' yesterday but the version apparently won't change until next Tuesday afternoon. I'm guessing it will change at some point in the future. Do I need to be on the dev channel already for this to work?) So I've tried 

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R23-23.0.1271.99/packages

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R23-2913.260.0/packages

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R23-2913.260/packages

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/chrome-R23-23.0.1271.99/packages

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/chrome-R23-2913.260.0/packages

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/chrome-R23-2913.260/packages

but none of them worked. Which URL exactly should I be using? I also tried the instructions at http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/install-software-on-base-images , but those didn't work either. It looks like 'M26' refers to milestone 26 on the Google Code page for Chromium, but it's hard to figure out when the fixes associated with that milestone will be released, even after reading http://www.chromium.org/releases/release-schedules; so I don't know whether I should even bother struggling with this.

Also, there was a question earlier about VT2 vs crosh. Does it matter which?

Many thanks,

Anand

[Mike Frysinger]

the form is:

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-<release>-<platform version>/packages

thus, with your M23 release and platform version of 2913.260.0, the correct URL:

https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R23-2913.260.0/packages

note that simply putting that into your browser and getting back a 404 isn't a valid test.  that is a directory, not a file, and google storage doesn't do directory listings.

you can "probe" for the "Packages" file:
$ HEAD https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R23-2913.260.0/packages/Packages

200 OK

crosh vs vt2 shouldn't make a difference

-mike

[Anand Patil]

Thanks for the help, Mike, that gets me past that initial error. As you inferred, I was checking the URL's by typing them into a browser.

Anand

[jchisholm]

Hi, I am still having trouble here. 

My version is:

Google Chrome	23.0.1271.111 (Official Build 175613)
Platform	2913.331.0 (Official Build) stable-channel x86-alex_he

Meaning my dev_install line is:

dev_install --binhost https://commondatastorage.googleapis.com/chromeos-dev-installer/board/x86-alex_he/canary-R23-2913.331.0/packages

And it seems to work. except everytime I --reinstall it, I end up not being able to `emerge chromeos-dev` it spits back 

------------------

!!! PORTAGE_BINHOST unset, but use is requested

Calculating Dependencies... Done!

 There are no ebuilds to satisfy "net-misc/iputils" for usr/local/

 Dependency required by .......

----------------

It seems that anything that has a dependency on something will always fail on me too. 

I notice that every time I run dev_install everything it downloads also has this little line:

[: 184: -ne: unexpected operator

In fact, everything that it downloads looks identical to m0g's original post, except that it does it a dozen or so times.

Are these two errors connected to each other?

Is there something wrong with my binhost?

am I missing a step?

Chris Sosa, you said you had this problem of it not resolving dependencies, What do you mean you can source /etc/profile ? 

that seemed to do nothing for me. after running that as a command I am still unable to emerge anything except things like gmerge

Thanks for help, tell me if you need more info. I would really like to be able to do this, or at least know why I can't

On Wednesday, January 23, 2013 12:55:39 PM UTC-8, Mike Frysinger wrote:

[Mike Frysinger]

On Sat, Jan 26, 2013 at 2:32 PM, jchisholm <jchi...@pvlearners.net> wrote:

And it seems to work. except everytime I --reinstall it, I end up not being able to `emerge chromeos-dev` it spits back 

------------------

!!! PORTAGE_BINHOST unset, but use is requested

Calculating Dependencies... Done!

 There are no ebuilds to satisfy "net-misc/iputils" for usr/local/

 Dependency required by .......

we aren't uploading that binpkg for some reason.  i've filed http://crosbug.com/38296 to track it.

 

I notice that every time I run dev_install everything it downloads also has this little line:

[: 184: -ne: unexpected operator

that's fixed in ToT and will make its way into releases

-mike

[Mike Frysinger]

On Mon, Jan 28, 2013 at 2:37 PM, Mike Frysinger <vap...@chromium.org> wrote:
> On Sat, Jan 26, 2013 at 2:32 PM, jchisholm <jchi...@pvlearners.net> wrote:
>> And it seems to work. except everytime I --reinstall it, I end up not
>> being able to `emerge chromeos-dev` it spits back
>> ------------------
>> !!! PORTAGE_BINHOST unset, but use is requested
>> Calculating Dependencies... Done!
>> There are no ebuilds to satisfy "net-misc/iputils" for usr/local/
>> Dependency required by .......
>
> we aren't uploading that binpkg for some reason. i've filed
> http://crosbug.com/38296 to track it.

good news: ToT (M26) will be fixed
bad news: not easy to fix older versions
ok news: you should be able to work around it by adding any package it
complains about to /usr/local/etc/portage/profile/package.provided.
list the full atom e.g. "net-misc/iputils-20100418-r3".
-mike

[jchisholm]

Cool updating to the dev channel and running dev_install again seemed to download that package! that the good news

The bad news is this is now happening to me :(

I run 

dev_install --reinstall --binhost https://commondatastorage.googleapis.com/chromeos-dev-installer/board/x86-alex_he/canary-R26-3658.0.0/packages

It does a bunch of downloading and extracting (then downloads this nice file you made available for me, thanks!) then it gives a 404 and even though it says that emerge was installed, emerge is most definitely, not installed. unless I am screwing this up somehow.

Downloading https://commondatastorage.googleapis.com/chromeos-dev-installer/board/x86-alex_he/canary-R26-3658.0.0/packages/net-misc/dhcp-4.2.2-r1.tbz2 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed100 2837k 100 2837k 0 0 343k 0 0:00:08 0:00:08 --:--:-- 379kExtracting /usr/local/portage/packages/net-misc/dhcp-4.2.2-r1.tbz2Files downloaded, configuring emerge. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (22) The requested URL returned error: 404Emerge installation complete. Installing additional optional packages.Install chromeos-dev package now (y/n)?You can install chromeos-dev later by typing the command: emerge chromeos-dev
localhost ~ # emerge chromeos-devbash: emerge: command not found

Every time I try to emerge anything it gives me that as though it has not been installed... Is the bash command just not aliased? where would I look? or is it something else?

[Mike Frysinger]

the 404 error is coming from an attempt to download a
packages.provided file from the server which normally does not exist.
so that isn't a problem.

emerge is not aliased. it is a program like any other. i'm not sure
why the --reinstall failed, but you can try doing:
rm -rf /usr/local/*
dev_install --binhost <that url>

and see if it works any better
-mike

[jchisholm]

Unfortunately that gave roughly the same result (also sorry about the formatting last time, hopefully this is a little better)

localhost ~ # rm -rf /usr/local/*

localhost ~ # dev_install --binhost https:/... 

...download stuff... extract....

Extracting /usr/local/portage/packages/net-misc/dhcp-4.2.2-r1.tbz2

Files downloaded, configuring emerge.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404

Emerge installation complete. Installing additional optional packages.
Install chromeos-dev package now (y/n)?y

/usr/bin/dev_install: 261: emerge: not found

localhost ~ # emerge chromeos-dev

bash: emerge: command not found

[Mike Frysinger]

do you have emerge in /usr/local/bin ?
-mike

[jchisholm]

There is a file called 'emerge' yes. don't know how to run it though ./emerge gives an error sh emerge gives a different error. If its not either of those than I am lost. do you want the output of either of those?

[jchisholm]

I half assume it is ./emerge. here is the error:

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

[Richard Barnette]

On Feb 13, 2013, at 5:04 PM, jchisholm <jchi...@pvlearners.net> wrote:

> I half assume it is ./emerge. here is the error:
>
> /usr/bin/python: error while loading shared libraries: libpython2.6.so.1.0: cannot open shared object file: No such file or directory
>

Hmmm... I just went through your earlier summary of what you did.
That included this command:

dev_install --reinstall --binhost https://commondatastorage.googleapis.com/chromeos-dev-installer/board/x86-alex_he/canary-R26-3658.0.0/packages

x86-alex_he names a model of the original Samsung Series 5
Chromebook. You say you're working with a new Samsung ARM
model. If that's so, then your problem is you're trying to execute
Intel binaries on an ARM system...

You'll need to use "daisy" in place of "x86-alex_he".

-- jrb

[jchisholm]

I went with alex because that what chrome://version says

(mind you, I am not the original poster here)

Google Chrome	26.0.1403.0 (Official Build 180337) dev
Platform	3658.0.0 (Official Build) dev-channel x86-alex_he
WebKit	537.30 (@141598)
JavaScript	V8 3.16.11.1
Flash	11.6.602.164

Etc.

But, I will give daisy a try anyway thank you

[jchisholm]

Running:

dev_install --reinstall --binhost https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/canary-R26-3658.0.0/packages

Gave me the same error...

..download ... extract...
Extracting /usr/local/portage/packages/net-misc/dhcp-4.2.2-r1.tbz2

Files downloaded, configuring emerge.
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404
Emerge installation complete. Installing additional optional packages.
Install chromeos-dev package now (y/n)?y
/usr/bin/dev_install: 261: emerge: not found

localhost bin # emerge chromeos-dev

bash: emerge: command not found

localhost bin #

On Wednesday, February 13, 2013 5:46:17 PM UTC-8, Richard Barnette wrote:

[Mike Frysinger]

the OP was using daisy which is why Richard suggested that.  you should pick the board name based on your chrome://version, so x86-alex_he is correct for you.

daisy will be arm based, so that isn't what you want.  fortunately, you'll only mess up /usr/local/ by picking the wrong board, so you can easily clean it all up.

-mike

[Richard Barnette]

On Feb 13, 2013, at 8:53 PM, jchisholm <jchi...@pvlearners.net> wrote:

> I went with alex because that what chrome://version says
> (mind you, I am not the original poster here)
>
> Google Chrome 26.0.1403.0 (Official Build 180337) dev
> Platform 3658.0.0 (Official Build) dev-channel x86-alex_he

If this is what your hardware says, then you don't have an ARM
chromebook, and using daisy won't help.

That said, one possible cause of the error you're reporting is
an ABI/ISA mismatch. That could be ARM vs. Intel; it can also
be 32-bit vs. 64-bit. It could also be that when the message
says "No such file or directory", it means it, and some file was
missing from the downloaded package.

[John Lawson]

Also getting the following error on a Chromebox after running various permutations of the dev_install and messing around with LD_LIBRARY_PATH:

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

Is this anything to do with the PYTHONPATH? Or perhaps to do with 32 vs 64 bit? I remember something similar to this happening when I started using Python on a server in our university department, but I can't recall exactly what the problem was.

Any help greatly appreciated.
John

[Mike Frysinger]

this thread has been hijacked a number of times already. please start
a new one.
-mike

[Shant Kehyeian]

Hey Mike ...
this link for binhost: https://commondatastorage.googleapis.com/chromeos-dev-installer/board/daisy/full-3.168.0.0/packages/, it isn't opening and isn't working.So do you have another binhost link which I could use ???...
Because it's giving me error :

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<Error>

<Code>NoSuchKey</Code>

<Message>The specified key does not exist.</Message>

</Error>

What does this mean ?

[Mike Frysinger]

this bug has been fixed a while ago.  update your chromebook to the latest stable channel.

-mike

--