RE: Windows Octave compilation

[John D]

-----Original Message-----
From: Tatsuro MATSUOKA [mailto:address@hidden 
Sent: Tuesday, July 08, 2014 11:09 PM
To: John D; John W. Eaton; address@hidden
Cc: PhilipNienhuis; address@hidden
Subject: Re: Windows Octave compilation



----- Original Message -----
> -----Original Message-----
> From: Tatsuro MATSUOKA [mailto:address@hidden
> Sent: Tuesday, July 08, 2014 8:44 PM
> To: address@hidden; John W. Eaton; John D; 
> address@hidden
> Cc: PhilipNienhuis; address@hidden
> Subject: Re: Windows Octave compilation
> 
>>  ----- Original Message -----
> 
>>>   From: John W. Eaton
>>>   To: Tatsuro MATSUOKA ; John D ; "address@hidden"
>>>   Cc: jwe; PhilipNienhuis; "tomasek.jan
>>>   Date: 2014/7/8, Tue 10:53
>>>   Subject: Re: Windows Octave compilation
>>> 
>>>   On 07/07/2014 08:23 PM, Tatsuro MATSUOKA wrote:
>>> 
>>>>    I have tried native build using Msys+MinGW toolchain (+
>>>   ghostscriot+python);
>>>> 
>>>>    I have met following error:
>>>> 
>>>>    [download] gnutls
>>>>    [build]    gnutls
>>>> 
>>>>    Failed to build package gnutls!
>>>>    ------------------------------------------------------------
>>>>    configure: error:
>>>>       ***
>>>>       *** Libnettle 2.7 was not found.
>>>>    make[1]: *** [build-only-gnutls] Error 1
>>>>    make[1]: Leaving directory
>>>   `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave'
>>>>    real    4m18.528s
>>>>    user    0m25.393s
>>>>    sys     0m58.869s
>>>>    ------------------------------------------------------------
>>>>    [log]
>>  /e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/log/gnutls
>>>> 
>>>>    make: ***
>>> 
>>  
>> [/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/installed-pack
>> a
>>  ges/gnutls]
>> 
>>>   Error 1
>>>> 
>>>>    This is first time for me to see a keyword nettle.
>>>>    Should nettle is build before gnutls on native windows?
>>> 
>>>   Did you update and build in a directory that contained a previous
> build?
> 
>>>     If so, this problem might be caused by having an old library  
>>> already  installed?
>>> 
>>>   jwe
>> 
>> 
>>  The previous build stropped due to python error (python 3.4 is not  
>> accepted. But I do not remember what reject python 3.4). I 
>> uninstalled  python 3.4 and installed python 2.7. After that I 
>> reconfigured and
> executed make.
>> 
>>  I will try again after I clean up all directory.
>> 
>>  Tatsuro
> 
> 
> I deleted all components and started again: The same error happens:
> 
> [build]    gnutls
> 
> Failed to build package gnutls!
> ------------------------------------------------------------
> configure: error:
>   ***
>   *** Libnettle 2.7 was not found.
> make[1]: *** [build-only-gnutls] Error 1
> make[1]: Leaving directory
> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave'
> real    4m1.822s
> user    0m25.237s
> sys     1m1.098s
> ------------------------------------------------------------
> [log]      
> /e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/log/gnutls
> 
> make: ***
> [/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/installed-packa
> ges/gn
> utls] Error 1
> 
> I think that this is fault of native windows build.
> 
> Tatsuro
> 
> 
> This is my first time to see about Libnettle. Perhaps most windows 
> user do not know it.
> If  Libnettle 2.7 is requirements, it should also be built before 
> gnutls build for MXE for native build.
> 
> Tatsuro
> 
> ---
> 
> When compiling native mxe, did you source tools/set-mxe-env.sh ?


I have executed tools/set-mxe-env.sh before "make" but the the result is not
that expected

seeing the environmental variable list by set command. 

I have looked into mxe-octave\usr\lib and found I have found
libnettle.dll.a.


I will manually execute the contents set-mxe-env.sh and see the reults.

Thanks

Tatsuro

--


It needs to be 'source tools/set-mxe-env.sh' rather than just executing
tools/set-mxe-env.sh