"James R. Phillips" wrote:
> This situation as regards gcc and octave is admittedly awkward, but I see no
> simple remedy as a package maintainer. It would be nice if gcc 3.4 were fixed
> - but I can't make that happen. It would be nice if cygwin supported multiple
> simultaneous gcc installs -
Re: jwe: what he said.
Also, this is a good time to remind cygwin package users that cygwin-specific
packaging notes for package foo-x are generally located in
/usr/share/doc/Cygwin/foo-x.README. This is a cygwin packaging standard - so
expect to find some information for every major installed pa
On 21-Feb-2006, Juhani Saastamoinen wrote:
| The binary octave modules compiled with gcc-3.4.4 don't work.
The last time I checked, Octave just doesn't work with gcc 3.4 on
Cygwin systems. I think the biggest problem is this bug
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24196
which was als
On 21 February 2006 11:41, Juhani Saastamoinen wrote:
> 4. Running octave with gdb suprisingly causes segmentation fault.
> The following happens, of course, indepent of the installed gcc version.
> This looks like some subtle problem, maybe with cygwin dll,
> octave, or gdb. Skillful people, pl
Hi,
The binary octave modules compiled with gcc-3.4.4 don't work.
Installing the gcc-3.3.3-3 compiler version makes oct modules
work again. I use a 'myones.cpp' code as an example below.
When debugging octave with gdb I saw even more subtle
problems which may be caused by cygwin, gdb, or octave.
5 matches
Mail list logo
