> Well i ran the make here and it was most satisfying to watch it go,
> i left it running in background, it was running for quite a while,
> when i checked back to see if had finished it had this on screen>
>
> Info: resolving vtable for __cxxabiv1::__cla
> TVN10__cxxabiv117__class_type_infoE (auto-im
> Info: resolving vtable for __cxxabiv1::__vmi
> ___ZTVN10__cxxabiv121__vmi_class_type_infoE
> e:/mingw/bin/../lib/gcc/mingw32/4.5.0/../../
> uto-importing has been activated without --e
> ommand line.
> This should work unless it involves constant
>  from auto-imported DLLs.
> === making documentation ===
> Formatting src/fltk.man...
> /bin/sh: man: command not found
> Formatting src/fltk-config.man...
> /bin/sh: man: command not found
> Formatting src/fluid.man...
> /bin/sh: man: command not found
> Formatting src/blocks.man...
> /bin/sh: man: command not found
> Formatting src/checkers.man...
> /bin/sh: man: command not found
> Formatting src/sudoku.man...
> /bin/sh: man: command not found
>
> pro...@au_vostro200_02 /e/mingw/fltk13
> $
>
> So does this mean that something in the documentation could not
> be completed but i expecwt everything else is ok?
>
> i have a lib folder full of lovely .a files so that means happy happy
> whatever!
>
>
the demo is mega! haha, i have not seen it like that before, just compiled and 
odd ones at random, test/demo different story though.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to