|
| From: | Jan Tomášek |
| Subject: | Re: Windows Octave compilation |
| Date: | Thu, 10 Jul 2014 19:56:19 +0200 |
---Sent: Thursday, July 10, 2014 4:03 AM
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/10, Thu 16:46
> Subject: RE: Windows Octave compilation -----Original Message-----
> From: Tatsuro MATSUOKA [mailto:address@hidden]
> Sent: Thursday, July 10, 2014 1:34 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
> <octave-maintainer>
>> Cc: PhilipNienhuis ; "tomasek.jan
>> Date: 2014/7/10, Thu 13:41
>> Subject: Re: Windows Octave compilation
>> ----- 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-pac
>>>> ka
>>>> ges/bu
>>>> ild-gcc', needed by
>>>>
>>>>
> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/installed-pac
>>>> ka
>>>> 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
>
>
> The build was stopped at early stage.(gawk that was built successfully
> in the previous try.)
>
> Failed to build package build-gawk!
> ------------------------------------------------------------
> make[3]: *** [gawkmisc.o] Error 1
> make[3]: Leaving directory
> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octae/tmp-build-gawk/gawk-4.1.1'
> make[2]: *** [mingw32] Error 2
> make[2]: Leaving directory
> `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octae/tmp-build-gawk/gawk-4.1.1'
> make[1]: *** [build-only-build-gawk] Error 2
>
> log:(related error)
> gcc -c -D__USE_MINGW_ANSI_STDIO -O2 -gdwarf-2 -g3 -DGAWK -I.
> -DHAVE_CONFIG_H -DDEFLIBPATH="\"c:/gnu/lib/gawk\""
> -DSHLIBEXT="\"dll\"" gawkmisc.c
>
> In file included from gawkmisc.c:36:0:
>
> pc/gawkmisc.pc:625:5: error: conflicting types for 'execvp'
> int execvp(const char *file, const char *const *argv)
> ^
>
> Tatsuro
>
> --
> Can you provide a larger sample of the log file as it should report
> where it is getting the conflicting defintions from.
I have attached the log file.
> Can you also try undoing my the gawk change and verify it would
> compile prior to that changeset?
Now I am trying. After finished, I will report here.
Also with the gawk changeset applied, try adding attached file to mxe-octave/src and see if it builds
| [Prev in Thread] | Current Thread | [Next in Thread] |