[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Windows Octave compilation
From: |
Tatsuro MATSUOKA |
Subject: |
Re: Windows Octave compilation |
Date: |
Thu, 10 Jul 2014 13:41:08 +0900 (JST) |
----- Original Message -----
> From: John D
> To: 'Tatsuro MATSUOKA' ; 'John W. Eaton' <address@hidden>; octave-maintainers
> Cc: 'PhilipNienhuis' ; tomasek.jan
> Date: 2014/7/10, Thu 12:48
> Subject: RE: Windows Octave compilation
>
>
>
> -----Original Message-----
> From: Tatsuro MATSUOKA [mailto:address@hidden
> Sent: Wednesday, July 09, 2014 10:25 PM
> To: John D; John W. Eaton; address@hidden
> Cc: PhilipNienhuis; address@hidden
> Subject: Re: Windows Octave compilation
>
> ----- Original Message -----
>
>> From: John D
>> To: 'Tatsuro MATSUOKA'; 'John W. Eaton' octave-maintainers
>> Cc: 'PhilipNienhuis' ; tomasek.jan
>> Date: 2014/7/9, Wed 19:20
>> Subject: RE: Windows Octave compilation
>>
>>
>>
>> -----Original Message-----
>> From: Tatsuro MATSUOKA [mailto:address@hidden
>> Sent: Wednesday, July 09, 2014 5:08 AM
>> To: John D; John W. Eaton; address@hidden
>> Cc: PhilipNienhuis; address@hidden
>> Subject: Re: Windows Octave compilation
>>
>> ----- Original Message -----
>>
>>> From: Tatsuro MATSUOKA
>>> To: John D John W. Eaton "octave-maintainers" <>
>>> Cc: PhilipNienhuis <"tomasek.jan
>>> Date: 2014/7/9, Wed 14:28
>>> Subject: Re: Windows Octave compilation
>>>
>>> ----- Original Message -----
>>>
>>>> From: John D > To: 'Tatsuro MATSUOKA' 'John W.
>> Eaton'
>>> octave-maintainers
>>>> Cc: 'PhilipNienhuis' tomasek.jan
>>>> Date: 2014/7/9, Wed 14:14
>>>> Subject: RE: Windows Octave compilation
>>>>
>>>>
>>>>
>>>> -----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-pac
>>>>> ka
>>>>> 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
>>>
>>>
>>> I have misled. Thanks! Now the make goes further after manually
>>> setting environmental variables in the tools/set-mxe-env.sh
>>>
>>> Next time I will do 'source tools/set-mxe-env.sh'.
>>>
>>> Tatsuro
>>>
>> After some proceed, I have met the following:
>>
>> :
>> [download] fontconfig
>> [build] fontconfig
>> [done] fontconfig
>> make: *** No rule to make target
>> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/installed-packa
>> ges/bu
>> ild-gcc', needed by
>> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/installed-packa
>> ges/gh
>> ostscript'. Stop.
>>
>> I do not find any 'ghostscript' in
>> /e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/installed-packages.
>>
>> Any suggestions?
>>
>> Tatsuro
>>
>> ----
>> Yeah - ghostscript is a new package - I haven’t gotten it to compile
>> natively yet.
>>
>> 1) change the ghostscript.mk file to not have build-gcc as a
>> dependency, and
>> add:
>> ifeq ($(USE_SYSTEM_GCC),no)
>> $(PKG)_DEPS += build-gcc
>> Endif
>>
>> 2) touch installed-packages/ghostscript
>>
>> 3) You will need a version of ghostscript installed on your computer
>> and include the pathtoghostscript/bin in your path.
>>
>
> I changed the ghostscript.mk file and try to build again:
>
>
> Failed to build package ghostscript!
> ------------------------------------------------------------
> ./obj/gscdefs.c:84:41: warning: unknown escape sequence: '\X'
> [enabled by default]
> ./obj/gscdefs.c:84:41: warning: unknown escape sequence: '\T'
> [enabled by default]
> make[2]: *** [obj/gscdefs.o] Error 1
> make[2]: Leaving directory
> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/tmp-ghostscript/ghostscript-9.07'
> make[1]: *** [build-only-ghostscript] Error 2
> make[1]: Leaving directory
> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave'
>
> I looked into the log file
> (Waring ignored)
> gcc -DHAVE_FILE64 -DHAVE_FSEEKO -DHAVE_FONTCONFIG -DHAVE_LIBIDN
> -DHAVE_SETLOCALE -DHAVE_BSWAP32 -DHAVE_STRERROR -O
> -I/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/usr/include -Wall
> -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes
> -Wwrite-strings -Wno-strict-aliasing -Wdeclaration-after-statement
> -fno-builtin
> -fno-common -DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_TIME_H=1
> -DHAVE_INTTYPES_H=1 -DGX_COLOR_INDEX_TYPE="unsigned long long"
> -DNOCONTRIB -DUSE_LIBICONV_GNU
> -Ie:/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/usr/include
> -I./obj
> -I./base -DWHICH_CMS="lcms2" -o ./obj/gscdefs.o -c ./obj/gscdefs.c
>
> ./obj/gscdefs.c:84:41: error: incomplete universal character name \u
>
>
> The ghostscript binary for windows is easily available.
> What is the reason ghostscript is built from source?
>
> Tatsuro
>
> ---
>
> I pushed a change up a couple of hours ago for ghostscipt to compile ok in
> Windows
Thanks!
I erased all components, cloned repository and started build.
Now I am in early stage for build.
After build will be finished or stopped, I will report here.
Tatsuro
- Re: Windows Octave compilation, (continued)
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/08
- RE: Windows Octave compilation, John D, 2014/07/08
- RE: Windows Octave compilation, John D, 2014/07/08
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/09
- RE: Windows Octave compilation, John D, 2014/07/09
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/09
- RE: Windows Octave compilation, John D, 2014/07/10
- Re: Windows Octave compilation, John W. Eaton, 2014/07/09
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/09
- RE: Windows Octave compilation, John D, 2014/07/09
- Re: Windows Octave compilation,
Tatsuro MATSUOKA <=
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/10
- RE: Windows Octave compilation, John D, 2014/07/10
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/10
- RE: Windows Octave compilation, John D, 2014/07/10
- Re: Windows Octave compilation, Jan Tomášek, 2014/07/10
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/10
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/10
- RE: Windows Octave compilation, John D, 2014/07/10
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/10
- Re: Windows Octave compilation, Tatsuro MATSUOKA, 2014/07/11