On Tue, Mar 4, 2014 at 4:11 AM, Peter Dolding <oia...@gmail.com> wrote:
> Basically as far as the main wine project knows no end user has an use
> for binfmt_misc loading .exe files. So to them its one of those
> bright spark ideas by package makers without any consideration to
> security.
I do.
>From my cmake build system setup, a test is simply a command line
application returning EXIT_SUCCESS / EXIT_FAILED.
$ cmake --help-command add_test
[...]
add_test(NAME testname COMMAND Exename arg1 arg2 ... )
[...]
Therefore I'd like to be able to use binfmt_misc just like any other
qemu-* (+binfmt_misc) simulated environment. Steps (within the *same*
machine, thanks to recent multiarch wine32/64 setup):
$ cat bla.c
int main() { return 0; }
$ i586-mingw32msvc-gcc -o bla.exe bla.c
$ export WINEPREFIX=~/wine32
$ ./bla.exe && echo "ok"
ok
$ x86_64-w64-mingw32-gcc -o bla2.exe bla.c
$ export WINEPREFIX=~/wine64
$./bla2.exe && echo "ok"
ok
This works very well for me and I like it this way, I can run cross
compilation + test executions targeting wine 32bits *and* 64bits .
This machine is a compilation machine, I have no issues with security
concerns.
2cts
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
