![]() |
Re: Disabling VDSO
Yes, your current user account.
$ sudo ./maemo-scratchbox-install_5.0.sh -u `whoami` |
Re: Disabling VDSO
Rakia, if you read here, it actually said that "Clarification needed: it's not clear to a first-timer whether this should be an existing user name from the host linux system, or a new user name for use only inside the scratchbox environment.]" on steps #3.
On step #5 it mentioned "Proceed further to run the Maemo SDK installer script. This script is run as 'user' outside the scratchbox environment. " if in step #3 I typed: $ sudo ./maemo-scratchbox-install_5.0.sh -u adhika can I run step #5 as user 'adhika' as well? what does "a user outside scratchbox environment" means? Thank you, Adhika |
Re: Disabling VDSO
Yes, that will work.
A user outside scratchbox environment means a working user account on the Linux system. Usually, that means the non-root account you're using. Your current account you're logged into on the Linux system is probably suitable. PS: the Maemo SDK documentation on wiki has been updated with clarifications regarding Linux x86-64 and disabling VDSO32. It should be easier with sysctl than editting bootloader such as GRUB(2). |
Re: Disabling VDSO
Thanks a lot Rakia, now I can see the desktop :)
|
Re: Disabling VDSO
(Hijacking the topic)
In case you're in Scratchbox1 compiling mood, you may want to test this patch which should fix the VDSO issue once for all. |
Re: Disabling VDSO
Quote:
If I understand this patches the libc6 which SB1 uses? I just checked, and my SB1 has a newer libc6 (although not as new as most recent Linux distributions), so its questionable whether it still patches and compiles clean since the patch patches a libc6 from 2005. Does SB2 also have this issue? What is the status of SB2? You may want to include this in the wiki. |
Re: Disabling VDSO
Quote:
Quote:
|
Re: Disabling VDSO
Quote:
|
Re: Disabling VDSO
Quote:
BTW, to use the above glibc patch you need to pull the whole sbox source (and it'll take a lot to build). |
Re: Disabling VDSO
Quote:
With deb-src I meant to do it in elegant way: 1) Add deb-src entry to get Scratchbox source to /etc/apt/sources.list 2) Exec apt-get -b source scratchbox (or whatever packages are required) 3) Add the patch in scratchbox-directory/debian/files 4) Build the .deb packages. If one don't care about dirty way then only 1 person just compiles that glibc w/patch and it'd be fixed, right? Not whole scratchbox is required to be recompiled then. Only stuff which linked to glibc static. |
All times are GMT. The time now is 15:57. |
vBulletin® Version 3.8.8