RE: trying to build gdb with renamed cygwin1.dll

I tried the -mno-cygwin option but got several compile
errors. I didn't
want to debug the sources because of time constraints. That
is why I
thought that compiling against a renamed cygwin1.dll might
be an eaisier
solution.

Fahd
 

-----Original Message-----
From: Andrew STUBBS [mailto:andrew.stubbsst.com] 
Sent: Monday, April 30, 2007 11:30 AM
To: Fahd Abidi
Cc: gdbsourceware.org
Subject: Re: trying to build gdb with renamed cygwin1.dll

Fahd Abidi wrote:
> My purpose is to try and build a gdb that so I can move
it across 
> different windows platforms with out worrying about
newer or older 
> versions of the cygwin dll interfering. I already
looked at the MinGW 
> option but the newer versions of gdb do not build
against mingw32.

I don't know about the exact solution you had in mind, but
....

You might want to investigate the -mno-cygwin GCC option.
This builds
"MinGW" binaries (Minimum GNU for Windows) which
do not depend upon
anything not present in a standard Windows installation.
This is how our
Windows tools are built.

Obviously there are issues with doing it this way - no
automatic support
for Cygwin pathnames being the biggest - but most of these
can be
overcome with little effort, and all overcome with more
effort.

Andrew

Fahd Abidi wrote:
> I tried the -mno-cygwin option but got several compile
errors. I didn't
> want to debug the sources because of time constraints.
That is why I
> thought that compiling against a renamed cygwin1.dll
might be an eaisier
> solution.

Well, it was never going to be easy! You might want to check
out 
mingw.org but I thought GDB was supposed to Just Work these
days.

I did have some problems with it autodetecting cygwin
ncurses, which 
obviously isn't going to work, but that can be fixed with 
--disable-readline ... probably. You can get readline to
work with 
pdcurses, but that required a little effort.

BTW, you just posted my email address, non-obfuscated, to
number of 
web-archives. I'd rather you didn't do that. It would
probably be best 
if you stopped your mailer doing that before you fully
spam-enable 
everybody else.

Andrew

Andrew STUBBS wrote:

> Well, it was never going to be easy! You might want to
check out
> mingw.org but I thought GDB was supposed to Just Work
these days.

I think the two of you are talking about two different
things.  It
sounds like he's trying to build a native debugger, and
you're talking
about a MinGW-hosted cross.  As far as I know (and I could
be wrong),
building a native MinGW gdb does not work currently and
hasn't for some
years, because it requires a ton of local patches that were
never
contributed.  The MinGW site indeed offers only a circa-2003
gdb v6.0
and a 2005 vintage v6.3, and that's it.

Brian

Brian Dessent wrote:
> I think the two of you are talking about two different
things.  It
> sounds like he's trying to build a native debugger, and
you're talking
> about a MinGW-hosted cross.  As far as I know (and I
could be wrong),
> building a native MinGW gdb does not work currently and
hasn't for some
> years, because it requires a ton of local patches that
were never
> contributed.  The MinGW site indeed offers only a
circa-2003 gdb v6.0
> and a 2005 vintage v6.3, and that's it.

Fair point, I am talking about my experience with a
cross-debugger.

He doesn't actually say what his debugger targets, but I had
assumed it 
was not native because, if he has Cygwin, he already has a
native GDB.

Sorry if I've confused the matter.

Andrew