[llvm-commits] [llvm] r145449 - in /llvm/trunk: CMakeLists.txt Makefile Makefile.rules autoconf/configure.ac configure tools/CMakeLists.txt tools/Makefile tools/llvm-config-2/BuildVariables.inc.in tools/llvm-config-2/CMakeLists.txt tools/llvm-config-2/Makefile tools/llvm-config-2/llvm-config.cpp tools/llvm-config/BuildVariables.inc.in tools/llvm-config/CMakeLists.txt tools/llvm-config/Makefile tools/llvm-config/find-cycles.pl tools/llvm-config/llvm-config.cpp tools/llvm-config/llvm-config.in.in

[Duncan Sands]

Hi Daniel, it looks like this commit broke the dragonegg buildbots, see
   http://lab.llvm.org:8011/builders/dragonegg-i386-linux/builds/538
   http://lab.llvm.org:8011/builders/dragonegg-x86_64-linux/builds/544
I think the reason for this is that when the old llvm-config was used from a
build tree, --cflags provided the include directory from the LLVM source:

   llvm-objects/Release+Debug+Asserts/bin/llvm-config --cflags
   -I/home/duncan/LLVM/llvm-objects/../llvm/include 
-I/home/duncan/LLVM/llvm-objects/include  -D_DEBUG -D_GNU_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -O3 
-fomit-frame-pointer -g -fPIC

Note the "-I/home/duncan/LLVM/llvm-objects/../llvm/include".  Judging by the
build logs, it looks like the new llvm-config is not doing that, and is only
providing the path to the build directory include, namely
"-I/home/duncan/LLVM/llvm-objects/include".

Ciao, Duncan.


> Author: ddunbar
> Date: Tue Nov 29 16:56:31 2011
> New Revision: 145449
>
> URL: http://llvm.org/viewvc/llvm-project?rev=145449&view=rev
> Log:
> llvm-config: Replace with C++ version (was llvm-config-2).
>   - Reapply of r144300, with lots of fixes/migration easement in between.