Thanks, applied.
On Sat, Jan 19, 2013 at 2:58 PM, Michael Tokarev wrote:
> Now, if seccomp is detected, it is linked into every executable,
> but is used only by softmmu targets (from vl.c). So link it
> only where it is actually needed.
>
> Signed-off-by: Michael Tokarev
> ---
> configure |
On Sat, Jan 19, 2013 at 8:58 AM, Michael Tokarev wrote:
> Now, if seccomp is detected, it is linked into every executable,
> but is used only by softmmu targets (from vl.c). So link it
> only where it is actually needed.
>
> Signed-off-by: Michael Tokarev
> ---
> configure |2 +-
> 1 file c
Il 19/01/2013 16:04, Michael Tokarev ha scritto:
>
>> Now, if seccomp is detected, it is linked into every executable,
>> but is used only by softmmu targets (from vl.c). So link it
>> only where it is actually needed.
>
> Note this is not just a cleanup. For some reason, at least
> debian pack
19.01.2013 18:58, Michael Tokarev wrote:
Now, if seccomp is detected, it is linked into every executable,
but is used only by softmmu targets (from vl.c). So link it
only where it is actually needed.
Note this is not just a cleanup. For some reason, at least
debian package of seccomp lacks st
Now, if seccomp is detected, it is linked into every executable,
but is used only by softmmu targets (from vl.c). So link it
only where it is actually needed.
Signed-off-by: Michael Tokarev
---
configure |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configur
