On 8 September 2015 at 16:19, Tom Stellard wrote:
> On Mon, Sep 07, 2015 at 10:06:49AM +0100, Emil Velikov wrote:
>> Hi Jon,
>>
>> On 4 September 2015 at 14:00, Jon TURNEY wrote:
>> > When checking for LLVM shared libraries, use IMP_LIB_EXT for the extension
>> > for
>> > shared libraries approp
On Mon, Sep 7, 2015 at 4:06 AM, Emil Velikov
wrote:
> Hi Jon,
>
> On 4 September 2015 at 14:00, Jon TURNEY
> wrote:
> > When checking for LLVM shared libraries, use IMP_LIB_EXT for the
> extension for
> > shared libraries appropriate to the target, rather than hardcoding '.so'
> >
> > Also add s
On Mon, Sep 07, 2015 at 10:06:49AM +0100, Emil Velikov wrote:
> Hi Jon,
>
> On 4 September 2015 at 14:00, Jon TURNEY wrote:
> > When checking for LLVM shared libraries, use IMP_LIB_EXT for the extension
> > for
> > shared libraries appropriate to the target, rather than hardcoding '.so'
> >
> >
On Fri, Sep 04, 2015 at 02:00:19PM +0100, Jon TURNEY wrote:
> When checking for LLVM shared libraries, use IMP_LIB_EXT for the extension for
> shared libraries appropriate to the target, rather than hardcoding '.so'
>
> Also add some comments to explain why we have this circus of pain.
>
> Signed
Hi Jon,
On 4 September 2015 at 14:00, Jon TURNEY wrote:
> When checking for LLVM shared libraries, use IMP_LIB_EXT for the extension for
> shared libraries appropriate to the target, rather than hardcoding '.so'
>
> Also add some comments to explain why we have this circus of pain.
>
> Signed-off
When checking for LLVM shared libraries, use IMP_LIB_EXT for the extension for
shared libraries appropriate to the target, rather than hardcoding '.so'
Also add some comments to explain why we have this circus of pain.
Signed-off-by: Jon TURNEY
---
configure.ac | 33 +++-
