|
From: | John Donoghue |
Subject: | Re: How can I make patch for mxe-build ? (was Re: Windows Octave compilation) |
Date: | Tue, 15 Jul 2014 21:06:22 -0400 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 07/15/2014 08:42 PM, Tatsuro MATSUOKA wrote:
I have posted: http://octave.1599824.n4.nabble.com/Re-Windows-Octave-compilation-td4665267i40.html#a4665493Failed to build package pstoedit! ------------------------------------------------------------ make[3]: *** [libpstoedit_la-dynload.lo] Error 1 make[3]: Leaving directory`/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/tmp-pstoedit/pstoedit-3.62/.build/src'make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory`/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/tmp-pstoedit/pstoedit-3.62/.build'make[1]: *** [build-only-pstoedit] Error 2 make[1]: Leaving directory `/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave' real 8m50.839s user 0m20.291s sys 1m49.394s ------------------------------------------------------------ [log]/e/usr/Tatsu/mingw32work/octave/mxe-octave/mxe-octave/log/pstoeditThe log file is attached.The origin of the error, very MS-win like functions, strcpy_s, andstrcat_s.These can be replaced by strncpy and strncat, respectively.Sorry I have mislead. MinGW-w64 (32 and 64 bit) has a definition verry MS like secure functions like (function name)_s. The definition of in pstoedit and MinGW-w64 seems to be inconsistent.To overcome this issue, the patch is needed. In src directory, there are patch files related to each dependency exist. For example, for gnuplot, gnuplot-1-fixes.patch and gnuplot-2-win64.patch exist and applied them before the build process. How can I make such patch for pstoedit? In the each mk file, patch file does not refer. Perhaps the procedure to apply is described elsewhere. How can I find this? Regards Tatsuro
They are automatically pulled in as part of Makefile.in rules.Create a patch pstoedit-X-YYYYY.patch and put it in the mxe-octave/src directory and it will be applied during the build.
X = sequence number for order to apply patches. YYYY = what patch is to fix in the package (or often just 'fixes')
[Prev in Thread] | Current Thread | [Next in Thread] |