Re: Compilation failure on Windows 7

[Jordi Gutiérrez Hermoso]

On 20 September 2012 08:00, Reza Housseini <address@hidden> wrote:
> I tried to compile on cygwin. The following error appeared:
>
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../libinterp -I..
> -I../../liboctave/cruft/misc -I../../liboctave/array -I../liboctave/numeric
> -I../../liboctave/numeric -I../liboctave/operators
> -I../../liboctave/operators -I../../liboctave/system -I../../liboctave/util
> -I../../libinterp/octave-value -I../../libinterp/operators -Iparse-tree
> -I../../libinterp/parse-tree -Iinterp-core -I../../libinterp/interp-core
> -Iinterpfcn -I../../libinterp/interpfcn -Icorefcn -I../libgnu -I../../libgnu
> -mieee-fp -I/usr/include/freetype2 -Wall -W -Wshadow -Wold-style-cast
> -Wformat -Wpointer-arith -Wwrite-strings -Wcast-align -Wcast-qual -g -O2 -MT
> interpfcn/interpfcn_libinterpfcn_la-graphics.lo -MD -MP -MF
> interpfcn/.deps/interpfcn_libinterpfcn_la-graphics.Tpo -c
> ../../libinterp/interpfcn/graphics.cc  -DDLL_EXPORT -DPIC -o
> interpfcn/.libs/interpfcn_libinterpfcn_la-graphics.o
> ../../libinterp/interpfcn/graphics.cc: In member function 'int
> gh_manager::do_process_events(bool)':
> ../../libinterp/interpfcn/graphics.cc:8206:17: error: 'Fdrawnow' was not
> declared in this scope
> Makefile:5795: recipe for target
> `interpfcn/interpfcn_libinterpfcn_la-graphics.lo' failed
> make[3]: *** [interpfcn/interpfcn_libinterpfcn_la-graphics.lo] Error 1
> make[3]: Leaving directory `/home/hous/workspace/octave/build/libinterp'
> Makefile:3409: recipe for target `all' failed
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/hous/workspace/octave/build/libinterp'
> Makefile:1952: recipe for target `all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/hous/workspace/octave/build'
> Makefile:1840: recipe for target `all' failed
> make: *** [all] Error 2
>
> It was building fine befor, so its not an dependency issue.

Please keep discussions about the development version on the
development list. It's in your best interest. The people who know the
context of this problem are not the people reading the help list. If
you follow the dev list, you may already see hints for how to address
this problem.

- Jordi G. H.