[lttng-dev] [Babeltrace PATCH] Remove extra -I for python bindings

2013-06-21 Thread Yannick Brosseau
Same fix as for lttng-tools commit f7cbc765ad2526667f1f20b3a89c596b3422ac34 Signed-off-by: Yannick Brosseau --- bindings/python/Makefile.am |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bindings/python/Makefile.am b/bindings/python/Makefile.am index 536e07f..b25ce92 1006

Re: [lttng-dev] [Babeltrace PATCH] Remove extra -I for python bindings

2013-06-21 Thread Mathieu Desnoyers
Merged into bindings/python branch. Thanks, Mathieu * Yannick Brosseau (yannick.bross...@gmail.com) wrote: > Same fix as for lttng-tools commit f7cbc765ad2526667f1f20b3a89c596b3422ac34 > > Signed-off-by: Yannick Brosseau > --- > bindings/python/Makefile.am |2 +- > 1 file changed, 1 inser

[lttng-dev] Compile failure on OSX 10.8

2013-06-21 Thread Anand Buddhdev
Hi people, I'm trying to compile userspace-rcu 0.7.7 on OSX 10.8.4, and it's failing. The configure phase completes, but make fails like this: $ make make all-recursive Making all in . CC wfqueue.lo CC wfstack.lo CC compat_arch_x86.lo /var/folders/9f/pv25pv1j7k54m9q11sz79w0h000

Re: [lttng-dev] Compile failure on OSX 10.8

2013-06-21 Thread Christian Babeux
Hi Anand, You might have to pass an additional host flag to configure e.g.: ./configure --host=i686-apple-darwin11 If I remember correctly, the compiler on OSX was compiled to run on a 64-bit platform but _only_ produce 32-bit binaries. Our configure script wrongly detect an x86-64 host, so you

Re: [lttng-dev] Compile failure on OSX 10.8

2013-06-21 Thread Anand Buddhdev
Hi Christian, OSX 10.8 *is* 64-bit. I often compile other stuff on it, and the compiler happily produces 64-bit binaries, for example: $ file ~/Homebrew/Cellar/mutt/1.5.21/bin/mutt /Users/anandb/Homebrew/Cellar/mutt/1.5.21/bin/mutt: Mach-O 64-bit executable x86_64 I've attached my config.log her

Re: [lttng-dev] Compile failure on OSX 10.8

2013-06-21 Thread Christian Babeux
Hmm that's really weird :/. For some reason configure detect an i386 CPU which is certainly not right. Could you post your config.log with and without the --host flag (specifying which is which)? There might be some slight incompatibilities on OSX and the CPU detection mechanism we are using... C