The attached patch makes this configurable at compile-time.
fwiw in scratchbox we have a wrapper in between binfmt and qemu (called
misc_runner) that sets any
necessary command line parameters for qemu. You might want to consider a
similar approach so we
don't need to add a configure
On Sun, Oct 25, 2009 at 06:49:44PM +0100, Jan-Simon Möller wrote:
We encontered problems with the low default value for the stacksize in
usermode (ok, whats low).
For environments like scratchbox, its hard to use -s as qemu is called by
binfmt mechanism.
The attached patch makes this
Hi !
We encontered problems with the low default value for the stacksize in usermode
(ok, whats low).
For environments like scratchbox, its hard to use -s as qemu is called by
binfmt mechanism.
The attached patch makes this configurable at compile-time.
Signed-off-by: Jan-Simon Möller
2009/10/25 Jan-Simon Möller dl...@gmx.de:
Hi !
We encontered problems with the low default value for the stacksize in
usermode (ok, whats low).
For environments like scratchbox, its hard to use -s as qemu is called by
binfmt mechanism.
The attached patch makes this configurable at
Am Sonntag 25 Oktober 2009 16:54:16 schrieb Laurent Desnogues:
Wouldn't it be better to set this earlier only if target_user_only
is set to yes and use cflags?
Something like this:
if test $target_user_only = yes -a $user_mode_stacksize != ; then
cflags=-DUSER_MODE_STACKSIZE $cflags
fi
We encontered problems with the low default value for the stacksize in usermode
(ok, whats low).
For environments like scratchbox, its hard to use -s as qemu is called by
binfmt mechanism.
The attached patch makes this configurable at compile-time.
Signed-off-by: Jan-Simon Möller dl...@gmx.de
Jan-Simon Möller wrote:
We encontered problems with the low default value for the stacksize in
usermode (ok, whats low).
For environments like scratchbox, its hard to use -s as qemu is called by
binfmt mechanism.
The attached patch makes this configurable at compile-time.
Note, this will