Reply
Thread Tools
Posts: 190 | Thanked: 129 times | Joined on Mar 2010 @ Bavaria, Germany
#1
Hello, I've just messed up my ubuntu-10.4 scratchbox vm and tried to recreate it.

I try that for two days now and it always stops with being unable to setup the armel target

One error of that:
Code:
Processing was halted because there were too many errors.
E: Sub-process /scratchbox/devkits/debian-etch/bin/dpkg returned an error code (1)
E: Unable to install maemo-sdk-dev on FREMANTLE_ARMEL target.
E: Please check the sources.list for errors.
E: Scratchbox login returned error 100.
Full log: http://gri.not-censored.com/maemo-sd...wizard_5.0.log

Is anyone else experiencing this problem? Maybe there is something updated for the next release? (The same installer with the same ubuntu image worked before ..)
 
Posts: 87 | Thanked: 47 times | Joined on Sep 2009 @ Sorocaba, Brasil
#2
The problem is not in scratchbox, which installs ok, but in the SDK installation inside scratchbox.

I have not been able to install the SDK since I updated to Lucid (10.04), with independence of the upgrading path (dist-upgrade or fresh install).

But I was not even able to install the last SDK 1.2 in Karmic (9.10), either, from scratch, though an installed one could be upgraded to 1.2

In my case it seems related to this bug: https://bugs.maemo.org/show_bug.cgi?id=9803

Could it be your case, too?
 

The Following User Says Thank You to dalonso For This Useful Post:
Posts: 190 | Thanked: 129 times | Joined on Mar 2010 @ Bavaria, Germany
#3
Originally Posted by dalonso View Post
The problem is not in scratchbox, which installs ok, but in the SDK installation inside scratchbox.

I have not been able to install the SDK since I updated to Lucid (10.04), with independence of the upgrading path (dist-upgrade or fresh install).

But I was not even able to install the last SDK 1.2 in Karmic (9.10), either, from scratch, though an installed one could be upgraded to 1.2

In my case it seems related to this bug: https://bugs.maemo.org/show_bug.cgi?id=9803

Could it be your case, too?
It seems to be the same, thanks. I keep watching the bug and hope it gets fixed soon.
 
Posts: 36 | Thanked: 43 times | Joined on Jan 2013
#4
I get this error in Fedora 17.
 
Posts: 1,203 | Thanked: 3,027 times | Joined on Dec 2010
#5
have you done the vdso_enabled = 0 and related sysconf changes on host machine?
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 09:19.