octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using 'llvm-config --ldflags' ?


From: Michael Goffioul
Subject: Re: Using 'llvm-config --ldflags' ?
Date: Wed, 1 Aug 2012 09:19:22 +0100

On Tue, Jul 31, 2012 at 7:51 PM, Jordi Gutiérrez Hermoso <address@hidden> wrote:
On 31 July 2012 14:40, Michael Goffioul <address@hidden> wrote:
> On Tue, Jul 31, 2012 at 7:04 PM, Jordi Gutiérrez Hermoso

>> Can Windows use pkg-config? I find llvm-config to be very badly
>> behaved, and I have half a mind to write llvm.pc. Will this work for
>> Windows?
>
> Yes, I have pkg-config, but afaik there's no llvm.pc coming with llvm, is
> it? At least it seems there's none on my F17 box with llvm-3.0. To be
> honest, I don't see the big deal in using --ldflags. It'll pull "-lffi
> -ldl"? So what...

llvm-config outputs the flags that were used to compile LLVM, not the
flags you need in order to compile against LLVM. So, for example, it
outputs -O2 -g on my system amidst its --cflags, which makes it
impossible to make a debug build. I'm not the first one to complain
about this:

    http://llvm.org/bugs/show_bug.cgi?id=4276
    http://llvm.org/bugs/show_bug.cgi?id=9405
    http://llvm.org/bugs/show_bug.cgi?id=8220

That's what.

Since we now care about LLVM, I'd like to fix its build system. Making
llvm.pc seems easier than trying to fix llvm-config.


Fair enough, though I was not talking about --cflags, but --ldflags. Now, if you manage (God knows when) to get pkg-config into llvm, this will make octave dependent on bleeding-edge not-yet-released LLVM. I think I'll go with a local/patchy solution instead.

Michael.
 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]