On Sat, Sep 25, 2010 at 12:24 PM, Xavier Chantry
chantry.xav...@gmail.com wrote:
On Fri, Sep 24, 2010 at 11:36 PM, Xavier Chantry
chantry.xav...@gmail.com wrote:
On Fri, Sep 24, 2010 at 3:15 PM, Luca Barbieri l...@luca-barbieri.com
wrote:
Yes, that used to happen for me too.
Just edit
On Fri, Sep 24, 2010 at 11:36 PM, Xavier Chantry
chantry.xav...@gmail.com wrote:
On Fri, Sep 24, 2010 at 3:15 PM, Luca Barbieri l...@luca-barbieri.com wrote:
Yes, that used to happen for me too.
Just edit llvm-config to remove the offending text and ideally file a
bug on the LLVM bug tracker.
When gallium llvm is enabled, configure.ac does the following :
LLVM_CFLAGS=`$LLVM_CONFIG --cflags`
This is the result on my system :
-I/usr/include -DNDEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -O2 -fomit-frame-pointer -fPIC
I specifically set -O0 to easier gdb
On Fri, Sep 24, 2010 at 14:06:51 +0200, Xavier Chantry wrote:
When gallium llvm is enabled, configure.ac does the following :
LLVM_CFLAGS=`$LLVM_CONFIG --cflags`
This is the result on my system :
-I/usr/include -DNDEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS
-D__STDC_CONSTANT_MACROS -O2
On Fri, Sep 24, 2010 at 3:15 PM, Luca Barbieri l...@luca-barbieri.com wrote:
Yes, that used to happen for me too.
Just edit llvm-config to remove the offending text and ideally file a
bug on the LLVM bug tracker.
looks like nobled did this for me : http://llvm.org/bugs/show_bug.cgi?id=8220