public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Ken Moore <KMoore@gse-inc.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: Hi,
Date: Wed, 21 Jun 2000 08:33:00 -0000	[thread overview]
Message-ID: <3950E045.93A97A18@cygnus.com> (raw)
In-Reply-To: <s950a1db.080@ait-udi.com>

(I don't know why I can't quote your original messages... HTML?)


Anyways, here it is:

 I did the install a week ago from the cygnus site.  The win98 "start menu" shows
 it as cygwin 1.1.0, but the downloaded tar.gz file shows it as 1.1.2.
  
Humm, this may have been an oversight. I will tell Cygwin people about it.
It doesn't hurt a thing though.

 I did "make install" from the insight directory. This ran to completion and put
 many files (and sub dirs) into the "cygwin\usr\local\share" directory.  gdb.exe
 itself is not moved anywhere.
  
Ken, you must go through the building instructions and the manual again.
A cross gdb will have an installed name that reflects the target platform.
The installed gdb will be m68k-elf-gdb.  Try it.  But before you do, look at
the following item.


 The gdb.exe wants the previously listed cyg*.dll files to run.  I had to manually
 locate these and copy them to a directory with gdb.exe. This didnt seem like a
 great thing to have to do, but it allowed the exe to run, otherwise it popped up a
 message box saying it could not find xxxx.dll.

This way you make absolutely certain thins will go wrong.  You must ensure, by all
means, that you don't have two copies of the DLL anywhere in your system.  And please 
note that they can be found in so many forms that the best way to ensure things
won't go wrong is having exactly one copy in your system (renaming to xxxx_dll, with
the underscore character also works.  adding things after the dll do not; deleting
the copies is safer).

Use the Find Windows utility to get rid of duplicates.

Use the "cygcheck -s" command to be sure the right ones are being picked.
If you need more help and post again, include that output as it may help.

But before posting, please, take a second look at the documentation: cygwin
and gdb.

Good luck!



-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com

  reply	other threads:[~2000-06-21  8:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-21  8:07 Hi, Ken Moore
2000-06-21  8:33 ` Fernando Nasser [this message]
2000-06-21  8:40 ` Hi, Chris Faylor
  -- strict thread matches above, loose matches on Subject: below --
2000-06-21 13:43 Hi, Ken Moore
2000-06-21  6:58 Hi, Ken Moore
2000-06-21  7:06 ` Hi, Fernando Nasser
2000-06-21 11:29 ` Hi, Jim Ingham
2000-06-21 12:52   ` Hi, Chris Faylor
2000-06-21 13:26     ` Hi, Jim Ingham
2000-06-21 13:48       ` Hi, Chris Faylor

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=3950E045.93A97A18@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=KMoore@gse-inc.com \
    --cc=insight@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).