RE: Re: GraphicsMagick 16bit on windows

[JohnD]

> -----Original Message-----
> From: Tatsuro MATSUOKA [mailto:address@hidden
> Sent: Saturday, July 04, 2015 9:22 AM
> To: JohnD; address@hidden
> Cc: address@hidden
> Subject: Re: Re: GraphicsMagick 16bit on windows
> 
> ----- Original Message -----
> 
> > From: JohnD
> > To: 'Tatsuro MATSUOKA' ; help-octave
> > Cc: jan.neggers
> > Date: 2015/7/4, Sat 20:10
> > Subject: RE: Re: GraphicsMagick 16bit on windows
> >
> >
> >
> >>  -----Original Message-----
> >>  From: Tatsuro MATSUOKA [mailto:address@hidden
> >>  Sent: Saturday, July 04, 2015 5:10 AM
> >>  To: JohnD; address@hidden
> >>  Cc: address@hidden
> >>  Subject: Re: Re: GraphicsMagick 16bit on windows
> >>
> >>  ----- Original Message -----
> >>
> >>  > From: JohnD
> >>  > To: help-octave
> >>  > Cc: tmacchant; jan.neggers
> >>  > Date: 2015/7/4, Sat 11:15
> >>  > Subject: RE: Re: GraphicsMagick 16bit on windows  >  >>  >>
> >> Message: 9  >>  Date: Sat, 4 Jul 2015 10:49:40 +0900 (JST)  >>  From:
> >> "address@hidden"
> > <address@hidden>
> >>  >>  To: address@hidden, address@hidden,  >>
> >> address@hidden  >>  Subject: Re: GraphicsMagick 16bit on windows  >>
> >> Message-ID: <address@hidden>
> >>  >>  Content-Type: text/plain; charset=iso-2022-jp  >>  >>  ---
> >> tmacchant  >>  > --- jan.neggers  >>  > > > On 03 Jul 2015, at 16:47,
> >> Marco Atzeri
> > <marco.atzeri On
> >>  > 7/3/2015
> >>  >>  > > > 11:49 AM, Jan Neggers wrote:
> >>  >>  > > >> I?m using octave 4.0 on windows 7, and I need
> > 16bit
> >>  > image support.
> >>  > I did
> >>  >>  install the 16bit version of GraphicsMagick, but how do I tell
> >> >> octave to  > use that  >>  version instead of the 8bit version
> >> provided with octave?
> >>  >>  > > >>
> > _______________________________________________
> >>  >>  > > >
> >>  >>  > > > You can't.
> >>  >>  > > >
> >>  >>  > > > So or you rebuild octave with 16bit version of  >
> >> GraphicsMagick or  >>  > > > you use the cygwin version that already
> >> has 16 bit
> > support.
> >>  >>  > >
> >>  >>  > > Ah, ok, I understand, I was more or less expecting this
> > answer,
> >>  > but
> >>  >>  sometimes we do get lucky! I?ll try to compile octave, but the
> >> >> problem is  > that  >>  this means all the students also have to
> >> do that, which is not  >> really an  > option.
> >>  >>  > >
> >>  >>  > > btw, the reason why we need 16bit support is because
> > the images
> >>  > are
> >>  > used
> >>  >>  as measurement data, i.e. computer-vision type problems, where
> > color
> >>  > precision
> >>  >>  does matter (the camera actually captures in 14bit).
> >>  >>  > >
> >>  >>  > >
> >>  >>  > >
> >>  >>  > Do you have or can use linux machine?
> >>  >>  > If not, I do not recommend to try to build octave on
> > windows.
> >>  >>  > Octave for native windows is now built by an tool called  >>
> >> mxe-octave on  > linux. Theoretically mxe-octave can be used on  >>
> >> windows but it is not  > easy as  >>  on linux. If you can use linux
> >> for mxe-octave build, I can give
> > you
> >>  > advises.
> >>  >>  > If you cannot, please wait JohnD's response.
> >>  >>  > He is the most working person on mxe-octave.
> >>  >>  >
> >>  >>  > BTW, I think that to use cygwin version of octave is
> > practical
> >>  > solution
> >>  > for the
> >>  >>  issue.
> >>  >>  >
> >>  >>  > Tatsuro
> >>  >>  >
> >>  >>
> >>  >>  For way to install octave-4.0.0 on cygwin,  see  >>  >>  >>
> > http://wiki.octave.org/Octave_for_Microsoft_Windows#Octave_4.0.0_on_c
> >>  >> yg
> >>  >>  win
> >>  >>
> >>  >>  Tatsuro
> >>  >>
> >>  >
> >>  > Mxe-octave should compile pretty much as is on msys2 (32 bit) with
the
> >>  > right tools installed, however takes many hours to compile, vs linux
> >>  > cross compile with can be done in a hour or two on a fast machine
> >>
> >>
> >>
> >>  John
> >>
> >>  Can you update MinGW part of below?
> >>  http://wiki.octave.org/Windows_Installer
> >>
> >>
> >>  I have not yet been gotten successful results (stopped at octave
build.).
> >>
> >>  Tatsuro
> >
> >
> > What error did you get at the octave build?
> >
> Error happened in compiling libgnu.
> 
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -
> I/c/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-stable-
> octave/octave-4.0.0/liboctave -I.. -I/c/usr/Tatsu/msys2_mingw32/mxe-
> octave32/mxe-octave/tmp-stable-octave/octave-4.0.0/liboctave/array -
> I/c/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-stable-
> octave/octave-4.0.0/liboctave/cruft/misc -Inumeric -
> I/c/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-stable-
> octave/octave-4.0.0/liboctave/numeric -Ioperators -
> I/c/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-stable-
> octave/octave-4.0.0/liboctave/operators -I/c/usr/Tatsu/msys2_mingw32/mxe-
> octave32/mxe-octave/tmp-stable-octave/octave-4.0.0/liboctave/system -
> I/c/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-stable-
> octave/octave-4.0.0/liboctave/util -I../libgnu -
> I/c/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-stable-
> octave/octave-4.0.0/libgnu -I/c/usr/Tatsu/msys2_mingw32/mxe-
> octave32/mxe-octave/usr/include -pthread -fopenmp
>  -mieee-fp -Wall -W -Wshadow -Wold-style-cast -Wformat -Wpointer-arith -
> Wwrite-strings -Wcast-align -Wcast-qual -g -O2 -MT
> system/system_libsystem_la-file-stat.lo -MD -MP -MF
> system/.deps/system_libsystem_la-file-stat.Tpo -c
> /c/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-stable-
> octave/octave-4.0.0/liboctave/system/file-stat.cc  -DDLL_EXPORT -DPIC -o
> system/.libs/system_libsystem_la-file-stat.o
> In file included from C:/msys64/mingw32/i686-w64-
> mingw32/include/sec_api/string_s.h:9:0,
>                  from
C:/msys64/mingw32/i686-w64-mingw32/include/string.h:181,
>                  from ../libgnu/string.h:27,
>                  from
C:/msys64/mingw32/i686-w64-mingw32/include/c++/cstring:42,
>                  from
C:/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-
> stable-octave/octave-4.0.0/liboctave/system/file-stat.cc:28:
> ../libgnu/time.h:465:45: error: conflicting declaration of 'tm*
localtime_r(const
> time_t*, tm*)' with 'C' linkage
>                                              _GL_ARG_NONNULL ((1, 2)));
>                                              ^
> In file included from ../libgnu/time.h:39:0,
>                  from ../libgnu/sys/stat.h:44,
>                  from
C:/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-
> stable-octave/octave-4.0.0/libgnu/filemode.h:22,
>                  from
C:/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-
> stable-octave/octave-4.0.0/liboctave/system/file-stat.cc:33:
> C:/msys64/mingw32/i686-w64-mingw32/include/time.h:269:34: note: previous
> declaration with 'C++' linkage
>  __forceinline struct tm *__cdecl localtime_r(const time_t *_Time, struct
tm
> *_Tm) {
>                                   ^
> In file included from C:/msys64/mingw32/i686-w64-
> mingw32/include/sec_api/string_s.h:9:0,
>                  from
C:/msys64/mingw32/i686-w64-mingw32/include/string.h:181,
>                  from ../libgnu/string.h:27,
>                  from
C:/msys64/mingw32/i686-w64-mingw32/include/c++/cstring:42,
>                  from
C:/usr/Tatsu/msys2_mingw32/mxe-octave32/mxe-octave/tmp-
> stable-octave/octave-4.0.0/liboctave/system/file-stat.cc:28:
> ../libgnu/time.h:487:42: error: conflicting declaration of 'tm*
gmtime_r(const
> time_t*, tm*)' with 'C' linkage
>                                           _GL_ARG_NONNULL ((1, 2)));
>                                           ^
> 
> Tatsuro

Ok - fixed that for default, but not on stable - you need to copy
src/mingw-octave-1-msys-fixes.patch to
src/mingw-stable-octave-1-msys-fixes.patch 

I believe it's an issue with 4.X+ of mingw  headers etc that has the issue -
cross mxe-octave still uses mingw 3.3.0.