Many thanks for your comments.
The core issue we’re running into is this:
$ GCC=/usr/bin/gcc LLVM_CONFIG=/usr/bin/llvm-config make
ld: fatal: library -lLLVMSupport: not found
ld: fatal: file processing errors. No output written to TargetInfo
collect2: error: ld returned 1 exit status
All other gyrations are attempts to shoehorn LLVMSupport into the compile. I’ve been sourcing the Makefile and README for hints.
To your point on declaring the location of gcc: Oddly, though gcc (4.7) is available to the environment, the Makefile does not find it without explicit direction:
make: cc: Command not found
Thanks in advance, Lou Picciano
(and apologies for the top posting; crappy email client)
First time attempting a build of dragonegg, using our shiny new install of
clang-3.3. I’m clearly off to a terrifying start!
This says to compile using gcc
This says that the plugin will be used with /usr/bin/gcc when built.
These say to use clang headers. Not sure why you want to use clang headers when
compiling using gcc.
In file included from /usr/clang/3.3/include/llvm/Support/DataTypes.h:67:0,
/usr/clang/3.3/lib/clang/3.3/include/stdint.h:32:54: error: missing binary
operator before token “(”
This seems to be saying that gcc doesn’t like the clang headers. I suggest you
don’t use them.
Anyway, not sure why you are trying to do this so complicated, doesn’t this
CXX is for providing a C++ compiler, so should be g++ not gcc
Since /usr/bin/gcc is in your path, probably you don’t need CXX to force this
compiler (or did you put clang in front of it in your path?; if so it still
shouldn’t be needed since clang can also compile dragonegg)
GCC=/usr/bin/gcc is probably not needed, since it is the default