Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Fahd Abidi'" <fabidi@ultsol.com>, 	<gdb@sourceware.org>
Subject: RE: trying to build gdb with renamed cygwin1.dll
Date: Mon, 30 Apr 2007 20:12:00 -0000	[thread overview]
Message-ID: <046901c78b63$cd990810$2e08a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <071DB0C788671B48940BC79F8B4930691181F6@ultsol01.tewks.ultsol.local>

On 30 April 2007 17:42, Fahd Abidi wrote:

> 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.

  You're putting an awful lot of effort into a mostly-imaginary problem.
Cygwin1.dll attempts to remain backwardly-compatible.  The last ABI break I
was remember was something to do with the __reent_impure pointer and it
happened sometime back around 1.5.3 IIRC.

  The one thing you can't do is carry around a copy of the cygwin dll that you
compiled against, and put gdb and that dll onto a system that already has a
different version of the dll installed; they will clash.

  But you shouldn't need to do that anyway; if there's an exisiting cygwin
install, you just need to copy gdb.exe across.  Apart from the occasional
break, as I mentioned above, /most/ versions of gdb compiled agsinst /most/
versions of the dll should work fine against /most/ other versions of the dll.
This is pretty much regardless of --disable-shared and --enable-static,
although if you compiled gdb against a very old or very new cygwin and the one
you're running it on doesn't have some of the same versions of the support
dlls you might find it's missing something, e.g. cygintl-1 vs. cygintl-2.
However, there's no compatibility problems between the differently-numbered
versions of the support dlls, so you should be able to carry a set of those
around and just leave out cygwin1.dll and get what you want.

  Give it a try if you haven't yet.  If you have, plese post the /exact/ error
message, so we can be clear precisely what situation you're talking about.



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


  parent reply	other threads:[~2007-04-30 20:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 16:38 Fahd Abidi
2007-04-30 17:04 ` Andrew STUBBS
2007-04-30 20:12 ` Dave Korn [this message]
2007-04-30 20:18   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2007-04-30 15:38 Fahd Abidi
2007-04-30 15:49 ` Andrew STUBBS
2007-04-30 15:57   ` Brian Dessent
2007-04-30 16:15     ` Andrew STUBBS
2007-04-30 15:05 Fahd Abidi
2007-04-30 15:10 ` Bob Rossi
2007-04-30 15:13   ` Bob Rossi
2007-04-30 15:18 ` Andrew STUBBS
2007-04-30 15:32 ` Brian Dessent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='046901c78b63$cd990810$2e08a8c0@CAM.ARTIMI.COM' \
    --to=dave.korn@artimi.com \
    --cc=fabidi@ultsol.com \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox