All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Novotny <minovotn@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: Xen-unstable-staging compilation error
Date: Fri, 24 Sep 2010 12:41:05 +0200	[thread overview]
Message-ID: <4C9C8041.5060708@redhat.com> (raw)
In-Reply-To: <4C9A10E1.4060804@redhat.com>

Well, I've been able to solve this one by adding "typedef int 
Py_ssize_t;" since I was using Python 2.4.3 that doesn't support 
Py_ssize_t natively. However, reinstalling the python was not the option 
because of the system dependencies so I downloaded source code for 
Python-2.7 and investigated this further. There was a definition of 
Py_ssize_t as int so I did just add this definition in 
/usr/include/python-2.4/Python.h file and the compilation was successful.

Hope this helps to someone as well,
Michal

On 09/22/2010 04:21 PM, Michal Novotny wrote:
> Hi,
> I've been trying to compile latest Xen-unstable staging on the x86_64 
> machine but I was getting following errors:
>
> creating build/temp.linux-x86_64-2.4/xen/lowlevel/flask
> gcc -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall 
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -O1 
> -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g 
> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
> -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD 
> -MF .buildpy.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fPIC 
> -I../../tools/libxc -I../../tools/xenstore -I../../tools/include 
> -I../../tools/libxl -Ixen/lowlevel/flask -I../flask/libflask/include 
> -I/usr/include/python2.4 -c xen/lowlevel/flask/flask.c -o 
> build/temp.linux-x86_64-2.4/xen/lowlevel/flask/flask.o 
> -fno-strict-aliasing -Werror
> gcc -pthread -shared -O1 -fno-omit-frame-pointer 
> -fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99 
> -Wall -Wstrict-prototypes -Wno-unused-value 
> -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .buildpy.d 
> -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
> build/temp.linux-x86_64-2.4/xen/lowlevel/flask/flask.o 
> -L../../tools/libxc -L../../tools/xenstore -L../../tools/libxl 
> -L../../tools/blktap2/control -L../flask/libflask -lxenctrl -lxenguest 
> -lxenstore -lflask -o build/lib.linux-x86_64-2.4/xen/lowlevel/flask.so
> building 'xl' extension
> creating build/temp.linux-x86_64-2.4/xen/lowlevel/xl
> gcc -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall 
> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -O1 
> -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g 
> -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
> -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD 
> -MF .buildpy.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fPIC 
> -I../../tools/libxc -I../../tools/xenstore -I../../tools/include 
> -I../../tools/libxl -Ixen/lowlevel/xl -I/usr/include/python2.4 -c 
> xen/lowlevel/xl/xl.c -o 
> build/temp.linux-x86_64-2.4/xen/lowlevel/xl/xl.o -fno-strict-aliasing 
> -Werror
> xen/lowlevel/xl/xl.c: In function ‘genwrap__obj_init’:
> xen/lowlevel/xl/xl.c:59: error: ‘Py_ssize_t’ undeclared (first use in 
> this function)
> xen/lowlevel/xl/xl.c:59: error: (Each undeclared identifier is 
> reported only once
> xen/lowlevel/xl/xl.c:59: error: for each function it appears in.)
> xen/lowlevel/xl/xl.c:59: error: expected ‘;’ before ‘pos’
> xen/lowlevel/xl/xl.c:64: error: ‘pos’ undeclared (first use in this 
> function)
> xen/lowlevel/xl/xl.c: In function ‘fixed_bytearray_set’:
> xen/lowlevel/xl/xl.c:170: error: ‘Py_ssize_t’ undeclared (first use in 
> this function)
> xen/lowlevel/xl/xl.c:170: error: expected ‘;’ before ‘ssz’
> xen/lowlevel/xl/xl.c:171: error: ‘ssz’ undeclared (first use in this 
> function)
> error: command 'gcc' failed with exit status 1
> make[3]: *** [buildpy] Error 1
> make[3]: Leaving directory 
> `/home2/shared/xen-unstable-staging/tools/python'
> make[2]: *** [subdir-install-python] Error 2
> make[2]: Leaving directory `/home2/shared/xen-unstable-staging/tools'
> make[1]: *** [subdirs-install] Error 2
> make[1]: Leaving directory `/home2/shared/xen-unstable-staging/tools'
>
> Any ideas?
>
> Michal
>


-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

      parent reply	other threads:[~2010-09-24 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 14:21 Xen-unstable-staging compilation error Michal Novotny
2010-09-23 18:12 ` Ian Jackson
2010-09-24 10:41 ` Michal Novotny [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=4C9C8041.5060708@redhat.com \
    --to=minovotn@redhat.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.