Re: Octave 3.8.2 released - llvm

[Tatsuro MATSUOKA]

----- Original Message -----
> From: John D 
> To: 'Tatsuro MATSUOKA' ; address@hidden
> Cc: 
> Date: 2014/8/26, Tue 09:29
> Subject: RE: Octave 3.8.2 released - llvm
> 
> 
> 
> -----Original Message-----
> From: Tatsuro MATSUOKA [mailto:address@hidden 
> Sent: Monday, August 25, 2014 7:41 PM
> To: John D; address@hidden
> Subject: Re: Octave 3.8.2 released - llvm
> 
> ----- Original Message -----
> 
>>  From: John D
>>  To: 'Tatsuro MATSUOKA' ; address@hidden
>>  Cc: 
>>  Date: 2014/8/26, Tue 08:29
>>  Subject: RE: Octave 3.8.2 released - llvm -----Original Message-----
>>  From: Tatsuro MATSUOKA [mailto:address@hidden
>>  Sent: Monday, August 25, 2014 7:27 PM
>>  To: John D; address@hidden
>>  Subject: Re: Octave 3.8.2 released - llvm
>>  ----- Original Message -----
>> 
>>>   From: John D
>>>   To: 'Tatsuro MATSUOKA' ; address@hidden
>>>   Cc: 
>>>   Date: 2014/8/25, Mon 19:39
>>>   Subject: RE: Octave 3.8.2 released - llvm -----Original Message-----
>>>   From: Tatsuro MATSUOKA [mailto:address@hidden
>>>   Sent: Monday, August 25, 2014 5:21 AM
>>>   To: John D; address@hidden
>>>   Subject: Re: Octave 3.8.2 released - llvm
>>> 
>>>>>    To my knowledge, Octave-3.8 does not support llvm-3.4.I am 
> using
>>>>>    llvm-3.2
>>> 
>>>>>    built myself. Perhaps, llvm-3.3 is OK for Octave-3.8 though I 
> 
>>>>>  have
>>>>>    not tested yet.
>>>>>    The develepment version octave perhaps supports llvm-3.4. 
> Perhaps
>>>>>    much experienced persons will give the correct replies.
>>>>    ---
>>>> 
>>>>    It was fixed in the devel version [1]
>>>> 
>>>>    [1] http://savannah.gnu.org/bugs/?41061
>>>> 
>>> 
>>>   As I wrote, I could not build the develoment soource of octave  
>>>  (changeset
>>>   19048:ec28b7216501) with llvm-3.4.2.
>>> 
>>>   
>>>  http://octave.1599824.n4.nabble.com/Octave-3-8-1-Released-td4662831.h
>>>  t
>>>   ml#a4666164
>>> 
>>>   The configration
>>>   cd ~/work/Octave/develop/build
>>> 
>>>   PATH=$PATH:/opt/clang+llvm-3.4.2/bin ../octave/configure 
>>>  --enable-jit  --prefix=/opt/octave-dev \  
>>>  LLVM_CONFIG=/opt/clang+llvm-3.4.2/bin/llvm-config
>>>   \ CPPFLAGS="-I/usr/include/mpi -DMPICH_SKIP_MPICXX
>>  -DOMPI_SKIP_MPICXX"
>>> 
>>>   PATH=$PATH:/opt/clang+llvm-3.4.2/bin LC_ALL=C make
>>> 
>>>   7-zipped config.log is attached.
>>>   Perhaps my build of clang+llvm-3.4.2 might be wrong.
>>> 
>>>   Any suggestions?
>>> 
>>>   # If I use clang+llvm-3.3, octave build was done w/o problem.
>>> 
>>>   Tatsuro
>>> 
>>>   --
>>>   What was the hg head changeset and which branch?
>> 
>>  I do not know what is hg head changeset and branch name.
>> 
>>  How can I see from the cloned source?
>> 
>> 
>>  I cloned repository at Aug.25, 2014 by:
>>  hg clone http://www.octave.org/hg/octave (perhaps I have cloned the 
>>  default branch? Right?)
>> 
>>  At the time I accessed http://www.octave.org/hg/octave I found that 
>>  top of the changeset.
>>  changeset 19048:ec28b7216501
>>  test.m: Overhaul function (also fixes bug #39703).
>> 
>>  I used gcc-4.8.2 (Ubuntu 14.04 LTS amd64).
>> 
>>  Tatsuro
>> 
>>  --
>>  hg head  - which would show the top change set hg branch - show the 
>>  current branch
> 
> Hmmm. I failed the above commands because ".hg" is missing in the 
> cloned
> directory.
> 
> 
>>  Do you have the config.log from running configure
> 
> That was already attached (7-zipped) in the first mail.
> I show the Nabble address to get it.
> 
> http://octave.1599824.n4.nabble.com/Re-Octave-3-8-2-released-llvm-td4666106.
> html#a4666195
> The last part of the pointed post you can see:
> (config.log.7z (92K) Download Attachment)
> 
> Tatsuro
> 
> --
> 
> How did you configure llvm ?

~/work/clang+llvm/llvm-3.4.2.src : source directory
The clang directory is copied to ~/work/clang+llvm/llvm-3.4.2.src/tools/clang

~/work/clang+llvm/build-3.4.2 : build directory

Configure:
cd ~/work/clang+llvm/build-3.4.2
../llvm-3.4.2.src/configure --prefix=/opt/clang+llvm-3.4.2

Tatsuro