qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: lejeczek <peljasz@yahoo.co.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-seccomp.c:228: error: '__NR_getcpu' undeclared here (not in a function)
Date: Thu, 16 Jan 2014 14:02:54 -0200	[thread overview]
Message-ID: <52D802AE.5060308@linux.vnet.ibm.com> (raw)
In-Reply-To: <52C6CF34.4030207@yahoo.co.uk>



On 01/03/2014 12:54 PM, lejeczek wrote:
> dear developers
>
> I was hoping someone could suggest what is missing or incompatible on my
> setup that causes a compilation to fail
>
> I'm trying to rpmbuild-compile qemu-1.2.2-1.fc18.src.rpm on rhel 6.5
> I thought I have got all dependencies from rpm perspective, naturally
> there is something wrong
> I think here is where it fails
>
> gcc
> -I/home/pe243/rpmbuild/BUILD/coruscant.ccnr.biotechnology/.el6/qemu-kvm-1.2.0/slirp
> -I. -I/home/pe243/rpmbuild/BUILD/coruscant.ccnr.biotec
> hnology/.el6/qemu-kvm-1.2.0
> -I/home/pe243/rpmbuild/BUILD/coruscant.ccnr.biotechnology/.el6/qemu-kvm-1.2.0/fpu
> -I/home/pe243/rpmbuild/BUILD/cor
> uscant.ccnr.biotechnology/.el6/qemu-kvm-1.2.0/libcacard -fPIE -DPIE -m64
> -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-pro
> totypes -Wredundant-decls -Wall -Wundef -Wwrite-strings
> -Wmissing-prototypes -fno-strict-aliasing -O2 -g -pipe -Wall
> -Wp,-D_FORTIFY_SOURCE=2 -
> fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64
> -mtune=generic -fPIE -DPIE  -fstack-protector-all -Wendif-labels
> -Wmissing-includ
> e-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k
> -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-defin
> ition -Wtype-limits -I/usr/include/libpng12 -I/usr/include/spice-server
> -I/usr/include/cacard -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/
> include -I/usr/include/pixman-1 -I/usr/include/nss3 -I/usr/include/nspr4
> -I/usr/include/spice-1 -I/usr/include/nss3 -I/usr/include/nspr4   -
> pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include
> -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/home/pe
> 243/rpmbuild/BUILD/coruscant.ccnr.biotechnology/.el6/qemu-kvm-1.2.0/include
> -MMD -MP -MT qemu-seccomp.o -MF ./qemu-seccomp.d -O2 -D_FORTIFY_SO
> URCE=2 -g  -c -o qemu-seccomp.o qemu-seccomp.c
> qemu-seccomp.c:228: error: '__NR_getcpu' undeclared here (not in a
> function)
>

My guess is that this is an old version that was bogusly dependent to 
linux headers. Can you check that?

(sorry for the late reply, I was on vacations until yesterday)

> what can be wrong?
> perhaps interestingly package qemu-1.2.0-22.fc19.src.rpm
> rpmbuild-comiles fine
>
> best regards
>
>

-- 
Eduardo Otubo
IBM Linux Technology Center

      reply	other threads:[~2014-01-16 16:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 14:54 [Qemu-devel] qemu-seccomp.c:228: error: '__NR_getcpu' undeclared here (not in a function) lejeczek
2014-01-16 16:02 ` Eduardo Otubo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D802AE.5060308@linux.vnet.ibm.com \
    --to=otubo@linux.vnet.ibm.com \
    --cc=peljasz@yahoo.co.uk \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).