octave-maintainers
[Top][All Lists]
Advanced

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

Re: build problems with AMCOND_HAVE_LLVM


From: Rik
Subject: Re: build problems with AMCOND_HAVE_LLVM
Date: Wed, 22 Jan 2014 22:49:45 -0800

On 01/22/2014 07:16 PM, address@hidden wrote:
> Message: 7
> Date: Wed, 22 Jan 2014 20:52:40 -0500
> From: Ben Abbott <address@hidden>
> To: Jordi Guti?rrez Hermoso <address@hidden>
> Cc: octave maintainers mailing list <address@hidden>
> Subject: Re: LYH's jit changes pushed
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Jan 22, 2014, at 12:58 PM, Jordi Guti?rrez Hermoso <address@hidden> wrote:
>
>> > Just FYI, I have pushed LYH's GSoC 2013 JIT work, as reworked by
>> > Stefan Mahr. This includes the possibly dubious new jit rule for make
>> > check:
>> > 
>> >    http://hg.savannah.gnu.org/hgweb/octave/graph/c3f3fa5a5db5
>> > 
>> > - Jordi G. H.
> After a pull, I'm seeing the problem below.
>
> checking for ftruncate... yes
> checking for mmap... (cached) yes
> checking for munmap... yes
> checking that generated files are newer than configure... done
> configure: error: conditional "AMCOND_HAVE_LLVM" was never defined.
> Usually this means the macro was only invoked conditionally.
>
> Is this expected? ... workaround?
I pushed a changeset to fix this
(http://hg.savannah.gnu.org/hgweb/octave/rev/7a1a71e3f328).  The warning
message was accurate; The AM_CONDITIONAL call was located within a larger
if block and so there were certain circumstances when it was never defined.

--Rik


reply via email to

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