RE: trying to build gdb with renamed cygwin1.dll

["Fahd Abidi" <fabidi@ultsol.com>]

Actually I am planning on eventually building a cross debugger for
arm/ppc/mips/xscale. But that will be afterwards. Right now I am just
trying to get the gdb binary to be stand alone. Actually I had allot of
success with building with the --disable-shared and --enable-static
option and was able to move the resulting gdb across different versions
of cygwin1.dll without it complain about using an incompatible version
of cygwin1.dll.

I think I will use this and play some games with a batch script and
figure out how to detect an existing version of cygwin1.dll then use
that info to decide whether to install my own version before gdb starts
up. Sounds like that will be the easiest solution.

Thanks for all the help. Sorry if I posted your email will be more
careful in the future. Is there a moderator here that can remove the
email address from my previous post?

thanks,

Fahd
 

-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] On
Behalf Of Andrew STUBBS
Sent: Monday, April 30, 2007 12:30 PM
To: gdb@sourceware.org
Cc: Fahd Abidi
Subject: Re: trying to build gdb with renamed cygwin1.dll

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