Reply
Thread Tools
Posts: 60 | Thanked: 73 times | Joined on Oct 2009 @ troll cave
#11
 

The Following User Says Thank You to suihkulokki For This Useful Post:
Posts: 123 | Thanked: 21 times | Joined on Sep 2009
#12
Originally Posted by MohammadAG View Post
Wonderful find mate! Works for me after doing it.
Now in wiki: http://wiki.maemo.org/Documentation/...d_distribution
FWIW, I didn't have to do 1 or 2, just 3, 4, 5, and 6 and it then worked with the SDK I already had installed.
 
Posts: 6 | Thanked: 0 times | Joined on May 2010
#13
Hi,

I used the GUI installer and I did as mentioned here by andy80, so there is no problem installing the sdk. but I still can't run the xephyr emulator, I tried using the shortcut on the desktop and I tried to run in terminal but failed to initiate it.
 
Posts: 190 | Thanked: 129 times | Joined on Mar 2010 @ Bavaria, Germany
#14
Originally Posted by kifcaliph View Post
Hi,

I used the GUI installer and I did as mentioned here by andy80, so there is no problem installing the sdk. but I still can't run the xephyr emulator, I tried using the shortcut on the desktop and I tried to run in terminal but failed to initiate it.
The shortcut doesn't work for me, too. Create your own desktop shortcut which calls "Xephyr -host-cursor -screen 800x480x16 :2".

Start Xephyr with it's new shortcut and then click the "Maemo SDK" shortcut on your desktop. It will start
 

The Following User Says Thank You to gri For This Useful Post:
Posts: 6 | Thanked: 0 times | Joined on May 2010
#15
ya it does work, thank you very much
 
Posts: 6 | Thanked: 0 times | Joined on May 2010
#16
I'd like to add that you can edit started_xephyr.sh located in /usr/local/bin/ with the code you provided or with this one here
 
Posts: 53 | Thanked: 51 times | Joined on Feb 2010
#17
Originally Posted by andy80 View Post
I've fixed the problem!

1) Use Synaptic and uninstall all scratchbox* packages

2) Remove /scratchbox directory

3) sudo vim /etc/sysctl.conf

4) Add this line: vm.mmap_min_addr = 0

5) Save and exit

6) sudo sysctl -p

That's all!

At this point just install Maemo SDK in the usual way and it will work. At least it did for me.
Fantastic, thank you very very much!!
 
Posts: 6 | Thanked: 0 times | Joined on Jan 2010 @ Leeds, UK
#18
Originally Posted by andy80 View Post
I've fixed the problem!

1) Use Synaptic and uninstall all scratchbox* packages

2) Remove /scratchbox directory

3) sudo vim /etc/sysctl.conf

4) Add this line: vm.mmap_min_addr = 0

5) Save and exit

6) sudo sysctl -p

That's all!

At this point just install Maemo SDK in the usual way and it will work. At least it did for me.
You don't need to uninstall the sdk or scratchbox, just add that line, reload the sysctl and carry on with the upgrade, that worked for me.

Thanks,
Luke.
 
Posts: 3,328 | Thanked: 4,476 times | Joined on May 2011 @ Poland
#19
I'm using Debian Squeeze 64 bit. I set up the first target flawlessly, and while setting up the 2nd target for experiments I'm getting this. Any ideas?

Code:
[sbox-fremantle2armel: ~] > fakeroot apt-get install -fReading package lists... Done
Building dependency tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
11 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up sudo (1.6.8p12-4osso22+0m5) ...
Updating sudoers
ERROR: ld.so: object '/usr/lib/libfakeroot-sysv/libfakeroot.so.0' from LD_PRELOAD cannot be preloaded: ignored.
visudo: you don't exist in the passwd database
/etc/sudoers.d/01sudo changes break sudoers
dpkg: error processing sudo (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of osso-af-startup:
 osso-af-startup depends on sudo; however:
  Package sudo is not configured yet.
dpkg: error processing osso-af-startup (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of osso-app-killer:
 osso-app-killer depends on osso-af-startup (>= 1.23); however:
  Package osso-af-startup is not configured yet.
 osso-app-killer depends on sudo; however:
  Package sudo is not configured yet.
dpkg: error processing osso-app-killer (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of ke-recv:
 ke-recv depends on osso-af-startup (>= 1.22); however:
  Package osso-af-startup is not configured yet.
dpkg: error processing ke-recv (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of hildon-application-framework-packages:
 hildon-application-framework-packages depends on osso-af-startup (>= 1.35-1); however:
  Package osso-af-startup is not configured yet.
 hildon-application-framework-packages depends on osso-app-killer; however:
  Package osso-app-killer is not configured yet.
 hildon-application-framework-packages depends on ke-recv; however:
  Package ke-recv is not configured yet.
dpkg: error processing hildon-application-framework-packages (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of hildon-application-framework:
 hildon-application-framework depends on hildon-application-framework-packages; however:
  Package hildon-application-framework-packages is not configured yet.
dpkg: error processing hildon-application-framework (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of hildon-application-framework-dev:
 hildon-application-framework-dev depends on hildon-application-framework; however:
  Package hildon-application-framework is not configured yet.
dpkg: error processing hildon-application-framework-dev (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maemo-core-runtime:
 maemo-core-runtime depends on sudo; however:
  Package sudo is not configured yet.
dpkg: error processing maemo-core-runtime (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maemo-core-dev:
 maemo-core-dev depends on maemo-core-runtime (= 5.0+3); however:
  Package maemo-core-runtime is not configured yet.
dpkg: error processing maemo-core-dev (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maemo-sdk-runtime:
 maemo-sdk-runtime depends on hildon-application-framework; however:
  Package hildon-application-framework is not configured yet.
 maemo-sdk-runtime depends on maemo-core-runtime; however:
  Package maemo-core-runtime is not configured yet.
dpkg: error processing maemo-sdk-runtime (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of maemo-sdk-dev:
 maemo-sdk-dev depends on maemo-sdk-runtime (= 5.0+0m5); however:
  Package maemo-sdk-runtime is not configured yet.
 maemo-sdk-dev depends on hildon-application-framework-dev; however:
  Package hildon-application-framework-dev is not configured yet.
 maemo-sdk-dev depends on maemo-core-dev; however:
  Package maemo-core-dev is not configured yet.
dpkg: error processing maemo-sdk-dev (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 sudo
 osso-af-startup
 osso-app-killer
 ke-recv
 hildon-application-framework-packages
 hildon-application-framework
 hildon-application-framework-dev
 maemo-core-runtime
 maemo-core-dev
 maemo-sdk-runtime
 maemo-sdk-dev
E: Sub-process /scratchbox/devkits/debian-etch/bin/dpkg returned an error code (1)
__________________
If you want to support my work, you can donate by PayPal or Flattr

Projects no longer actively developed: here

Last edited by marmistrz; 2012-06-23 at 09:40.
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 22:04.