[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-patch-tracker] [patch #8783] C++ implementation of textscan

From: Philip Nienhuis
Subject: [Octave-patch-tracker] [patch #8783] C++ implementation of textscan
Date: Sat, 05 Dec 2015 12:17:28 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0 SeaMonkey/2.38

Follow-up Comment #14, patch #8783 (project octave):

Well OTOH it is true that 45 of the 62-or-so tests SUCCEEDED :-)
Chances are the FAILs are due to specific MinGW idiosyncrasies and perhaps
some includes and stuff needed for MinGW that you (and I) weren't aware of.
(And that's only MinGW then; Mac OSX comes next.....)

I'll try to make a debug (unstripped) mxe-octave version with (x)textscan.cc
this weekend; I can put it up on my Dropbox. It'll have to be a zipped version
("make zipdist"), as a complete nsis-installer including OF packages is much
too big (> 2 GB seems to be problematic for MXE).

If you want to make an mxe-octave version yourself,  be sure to specify the
relevant configure options (see ./configure --help), i.e. development tools,
MSYS shell, gdb, do not strip binaries.
Once in Windows and doing "gdb octave-cli", don't be put off initially by the
many many C/CPP error messages about wrong arguments and IIRC even a segfault,
after that octave-cli will start fine nonetheless.

As regards gdb I'm a novice so I'm of little help. I know debuggers only from
DOS assembly and Fortran program development (sic) long ago, but I assume the
principles are largely similar.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]