On Friday, April 10, 2015 05:40:40 PM Andreas Färber wrote:
> My main concern - that you apparently misunderstood - was whether this
> is a QEMU or a libseccomp issue. If it's on libseccomp's side then it's
> less urgent for QEMU and any new configure checks are just candy IMO.
My opinion is that
On Thursday, April 09, 2015 02:28:24 PM Andreas Färber wrote:
> Am 09.04.2015 um 11:10 schrieb Paul Moore:
> > On Thursday, April 09, 2015 10:21:52 AM Eduardo Otubo wrote:
> >> On Thu, Apr 09, 2015 at 05=01=31AM +0200, Andreas Färber wrote:
> >>> Hello,
> >>>
> >>> I am seeing the following build
Am 09.04.2015 um 11:10 schrieb Paul Moore:
> On Thursday, April 09, 2015 10:21:52 AM Eduardo Otubo wrote:
>> On Thu, Apr 09, 2015 at 05=01=31AM +0200, Andreas Färber wrote:
>>> Hello,
>>>
>>> I am seeing the following build failure on openSUSE Tumbleweed armv7l
>>> with --enable-seccomp in v2.3.0-r
On Thursday, April 09, 2015 10:21:52 AM Eduardo Otubo wrote:
> On Thu, Apr 09, 2015 at 05=01=31AM +0200, Andreas Färber wrote:
> > Hello,
> >
> > I am seeing the following build failure on openSUSE Tumbleweed armv7l
> > with --enable-seccomp in v2.3.0-rc2:
> >
> > [ 551s] In file included from q
On Thu, Apr 09, 2015 at 05=01=31AM +0200, Andreas Färber wrote:
> Hello,
>
> I am seeing the following build failure on openSUSE Tumbleweed armv7l
> with --enable-seccomp in v2.3.0-rc2:
>
> [ 551s] In file included from qemu-seccomp.c:16:0:
> [ 551s] /usr/include/libseccomp/seccomp.h:177:23: er
Hello,
I am seeing the following build failure on openSUSE Tumbleweed armv7l
with --enable-seccomp in v2.3.0-rc2:
[ 551s] In file included from qemu-seccomp.c:16:0:
[ 551s] /usr/include/libseccomp/seccomp.h:177:23: error: '__NR_mmap'
undeclared here (not in a function)
[ 551s] #define SCMP_SY
