Re: [sdcc-devel] mingw bugs: newbe question

[Johan K. <joh...@id...>]

> The build of mingw from Mumit Kahn is only 2.95.2, but it does include
> gdb.  Just gave it a quick run against the non-striped version my Linux
> box built and it seemed to work.
>
> See:
> http://www.nanotech.wisc.edu/~khan/software/gnu-win32/gcc.html

Ok, got that. Works fine.

Than I downloaded the latest cygwin (the whole package) because I needed a
bash, bison and flex; and made sure that mingw was used instead of the
standard gcc (gcc -v). Configure problems in cpp2 because of unterminated
strings, small problem. Than it turns out that the debugger only finds the
source files when they are in the current dir. Build problems with the
libraries, after adding "-V" to sdcc in the makefile: it calls sdcpp like
"/usr/local/bin\sdcpp" and couldn't find it. From within gdb it calls it
like "c:\cygwin\home\johan\sdcc\sdcpp". I spent a couple of hours on this,
but I quit. I can't even acces the history using cursor keys or e.g. ^R in
the debugger, nor can paste in the windows. This is a crime.

Johan

>
> -- Michael
>
> On Sat, 13 Oct 2001, Johan Knol wrote:
>
> > Hi,
> >
> > I noticed some bugreports that couldn't be reproduced on a linux (or ppc
:)
> > machine. So I downloaded the latest mingw binaries and indeed, they are
> > there. Using the mingw binaries there is ofcourse no way to debug the
> > compiler.
> >
> > Is there a machine on sourceforge.net that can run and debug mingw
compiled
> > sdcc (guess not, ms$win isn't a real os). If not, what is the minimum
that I
> > need to download from where (apart for the sdcc sources of course: a
> > compiler, yacc/bison and a gdb-compatible debugger).
> >
> > I don't want to spend too much time on this searching the web, so any
hints
> > are welcome.
> >
> > Thanks, Johan
> >
> >
> > _______________________________________________
> > sdcc-devel mailing list
> > sdc...@li...
> > https://lists.sourceforge.net/lists/listinfo/sdcc-devel
> >
>