error: unknown type name 'IRLoadGOp'

[joxeankoret]

Hi,

I'm trying to build pyvex in Ubuntu 12.04 x86_64 with the setup recommend in README.md. However, when I try to build it I get the following errors:

$ LANG=C sh build.sh 
running build
running build_ext
building 'pyvex' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/pyvex
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -DPYVEX_STATIC=1 -I/home/joxean/devel/valgrind/valgrind-3.8.1/install/include/valgrind -I/usr/include/python2.7 -c pyvex/pyvex.c -o build/temp.linux-x86_64-2.7/pyvex/pyvex.o --std=c99
In file included from pyvex/pyvex.c:7:0:
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
error: command 'gcc' failed with exit status 1
cp: cannot stat `build/lib.linux-x86_64-2.7/pyvex.so': No such file or directory
cp: cannot stat `pyvex.so': No such file or directory

Am I doing something wrong?

[zardus]

Thanks for trying PyVEX! What version of VEX are you using? PyVEX requires
VEX 3.9, which is newer than what's shipped with Ubuntu at the moment.

• Yan

On Sun, Apr 13, 2014 at 8:31 AM, Joxean notifications@github.com wrote:

Hi,

I'm trying to build pyvex in Ubuntu 12.04 x86_64 with the setup recommend
in README.md. However, when I try to build it I get the following errors:

$ LANG=C sh build.sh
running build
running build_ext
building 'pyvex' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/pyvex
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -DPYVEX_STATIC=1 -I/home/joxean/devel/valgrind/valgrind-3.8.1/install/include/valgrind -I/usr/include/python2.7 -c pyvex/pyvex.c -o build/temp.linux-x86_64-2.7/pyvex/pyvex.o --std=c99
In file included from pyvex/pyvex.c:7:0:
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
pyvex/pyvex_enums.h:18:1: error: unknown type name 'IRLoadGOp'
error: command 'gcc' failed with exit status 1
cp: cannot stat build/lib.linux-x86_64-2.7/pyvex.so': No such file or directory cp: cannot statpyvex.so': No such file or directory

Am I doing something wrong?

Reply to this email directly or view it on GitHubhttps://github.com//issues/6
.

[joxeankoret]

Hi,

VEX comes with Valgrind, right? In this case, I'm using the version that comes with Valgrind 3.8.1. I just followed the instructions here: https://github.com/zardus/pyvex/blob/master/README.md

[zardus]

Ah! Yeah, my readme is wrong. Sorry about that! You need Valgrind 3.9.0,
not 3.8.1. I updated the readme; thanks for pointing that out :-)

On Sun, Apr 13, 2014 at 11:04 PM, Joxean notifications@github.com wrote:

Hi,

VEX comes with Valgrind, right? In this case, I'm using the version that
comes with Valgrind 3.8.1. I just followed the instructions here:
https://github.com/zardus/pyvex/blob/master/README.md

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-40335484
.

[joxeankoret]

Hey, thanks! I resolved this issue. However, another one arised:

pyvex/pyvex_static.c: In function 'vex_init':
pyvex/pyvex_static.c:177:26: warning: assignment from incompatible pointer type [enabled by default]
pyvex/pyvex_static.c: In function 'vex_prepare_vai':
pyvex/pyvex_static.c:214:7: error: 'VexArchInfo' has no member named 'endness'
pyvex/pyvex_static.c:219:7: error: 'VexArchInfo' has no member named 'endness'
pyvex/pyvex_static.c:224:7: error: 'VexArchInfo' has no member named 'endness'
pyvex/pyvex_static.c:232:7: error: 'VexArchInfo' has no member named 'endness'
error: command 'gcc' failed with exit status 1

Any idea?

[joxeankoret]

BTW, commenting out the offending lines (with a comment saying "unsure if correct") was enough to get a working build of pyvex.

[zardus]

lol, that's definitely my fault. I was testing something with some VEX
patches I'm working on, and accidentally pushed it. Thank you for catching
that :-)

On Tue, Apr 15, 2014 at 1:38 AM, Joxean notifications@github.com wrote:

BTW, commenting out the offending lines (with a comment saying "unsure if
correct") was enough to get a working build of pyvex.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-40457816
.

[zardus]

I commented out the lines. Thanks!

[joxeankoret]

You're welcome! BTW, just a recommendation: it would be useful to have some example or use case for it.

[zardus]

Yeah, for sure! We are brewing up something in that direction. Stay tuned
;-)

On Thu, Apr 17, 2014 at 7:46 AM, Joxean notifications@github.com wrote:

You're welcome! BTW, just a recommendation: it would be useful to have
some example or use case for it.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/6#issuecomment-40721977
.