maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Development (https://talk.maemo.org/forumdisplay.php?f=13)
-   -   Disabling VDSO (https://talk.maemo.org/showthread.php?t=32696)

allnameswereout 2009-10-13 01:06

Re: Disabling VDSO
 
Yes, your current user account.

$ sudo ./maemo-scratchbox-install_5.0.sh -u `whoami`

adhika_rexuss 2009-10-13 01:25

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

allnameswereout 2009-10-13 08:55

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

adhika_rexuss 2009-10-13 13:55

Re: Disabling VDSO
 
Thanks a lot Rakia, now I can see the desktop :)

javispedro 2009-10-13 14:21

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.

allnameswereout 2009-10-14 12:21

Re: Disabling VDSO
 
Quote:

Originally Posted by javispedro (Post 345366)
(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.

(Totally ontopic IMO :D)

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.

javispedro 2009-10-14 12:36

Re: Disabling VDSO
 
Quote:

Originally Posted by allnameswereout (Post 346171)
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.

Newer? It's still 2.3.2 aka ancient. Check http://www.scratchbox.org/cgi-bin/da...glibc/Makefile . You're probably checking the chroot/target libc version, which should match the versions the devices use.

Quote:

Originally Posted by allnameswereout (Post 346171)
Does SB2 also have this issue?

No AFAIK.

allnameswereout 2009-10-15 16:04

Re: Disabling VDSO
 
Quote:

Originally Posted by javispedro (Post 346184)
Newer? It's still 2.3.2 aka ancient. Check http://www.scratchbox.org/cgi-bin/da...glibc/Makefile . You're probably checking the chroot/target libc version, which should match the versions the devices use.

True. Do you know a way to use APT with deb-src and Scratchbox? I'm now compiling it manually, and this is getting ugly.

javispedro 2009-10-15 16:11

Re: Disabling VDSO
 
Quote:

Originally Posted by allnameswereout (Post 347344)
True. Do you know a way to use APT with deb-src and Scratchbox? I'm now compiling it manually, and this is getting ugly.

I do not know what you mean with deb-src and Scratchbox...

BTW, to use the above glibc patch you need to pull the whole sbox source (and it'll take a lot to build).

allnameswereout 2009-10-18 20:32

Re: Disabling VDSO
 
Quote:

Originally Posted by javispedro (Post 347353)
I do not know what you mean with deb-src and Scratchbox...

BTW, to use the above glibc patch you need to pull the whole sbox source (and it'll take a lot to build).

Yeah I tried that but I have x86-64 bit environment on this machine.

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