Bug#573368: llvm-dev - Needs libffi-dev, but does not depend

[Bastian Blank]

On Sun, Apr 11, 2010 at 12:30:18PM +0200, Arthur Loiret wrote:
> 2010/3/10, Bastian Blank <waldi at debian.org>:
> > | # llvm-config --cflags --ldflags --libs jit engine
> > | -I/usr/include  -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS
> > -D__STDC_CONSTANT_MACROS -O2 -fomit-frame-pointer -fPIC
> > | -L/usr/lib/llvm/lib  -lpthread -lffi -ldl -lm
> > | -lLLVMX86AsmParser -lLLVMX86AsmPrinter -lLLVMX86CodeGen -lLLVMSelectionDAG
> > -lLLVMAsmPrinter -lLLVMX86Info -lLLVMJIT -lLLVMExecutionEngine -lLLVMCodeGen
> > -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMTarget
> > -lLLVMMC -lLLVMCore -lLLVMSupport -lLLVMSystem -L/usr/lib/llvm/lib

Oh, and while we are at it. The following specifications are
inappropriate or at least questionable.
-I/usr/include: Is already defined in the default include path and
changes the order.
-D_DEBUG: Names with underscores are reserved for the implementation.
The C implementation on a standard Debian system consists of glibc and
gcc and they don't use this name.
-D_GNU_SOURCE: Modifies the behaviour of the source.
-O2: This is up the application.
-fomit-frame-pointer: Makes debugging impossible.
-fPIC: Not applicable for binaries but may not fail on most
architectures.
-L/usr/lib/llvm/lib: I don't see an rpath, so all libs and the symlinks
needs to be located in one of the standard locations anyway.

Bastian

-- 
I'm a soldier, not a diplomat.  I can only tell the truth.
		-- Kirk, "Errand of Mercy", stardate 3198.9