From: Stephen Smith <ischis2@home.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: DJ Delorie <dj@redhat.com>, gdb@sourceware.cygnus.com
Subject: Re: GDB for PE/Cywin target won't build on linux
Date: Mon, 16 Jul 2001 14:27:00 -0000 [thread overview]
Message-ID: <3B535C6B.2B99791C@home.com> (raw)
In-Reply-To: <1010716193231.ZM31023@ocotillo.lan>
Once I added the the following patch to configure.tgt everything worked. Thanks for your help.
I will now be working on submitting the patches (for this and the re-submit from before).
[ssmith@az75-linuxbox gdb]$ diff -c -w -b -B configure.tgt.orig configure.tgt
*** configure.tgt.orig Tue Apr 17 14:20:48 2001
--- configure.tgt Mon Jul 16 14:00:00 2001
***************
*** 122,127 ****
--- 122,128 ----
configdirs="${configdirs} nlm" ;;
i[3456]86-*-osf1mk*) gdb_target=i386mk ;;
i[3456]86-*-cygwin*) gdb_target=cygwin ;;
+ i[3456]86-*-pe*) gdb_target=embed ;;
i[3456]86-*-vxworks*) gdb_target=vxworks ;;
i960-*-bout*) gdb_target=vxworks960 ;;
Kevin Buettner wrote:
> On Jul 16, 11:49am, Stephen Smith wrote:
> For your purposes, I think it'd be better to just use ``gdb_target=embed''.
> You'll avoid the shared library nightmares that way. If you find that
> you need some sort of shared library support, you'll have to implement
> it separately. (This'll likely mean creating a new *.mt file, a new
> tm-*.h file, and a new solib-*.c file which'll have the shared library
> support that you need.)
>
> Kevin
prev parent reply other threads:[~2001-07-16 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 15:50 x86-linux -> x86-pe GDB will not configure Stephen Smith
2001-07-13 12:22 ` GDB for PE/Cywin target won't build on linux Stephen Smith
2001-07-13 14:41 ` DJ Delorie
2001-07-13 15:02 ` Stephen Smith
[not found] ` <200107132206.SAA27799@greed.delorie.com>
2001-07-13 15:26 ` Stephen Smith
2001-07-16 11:49 ` Stephen Smith
2001-07-16 12:33 ` Kevin Buettner
2001-07-16 12:52 ` DJ Delorie
2001-07-16 14:27 ` Stephen Smith [this message]
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=3B535C6B.2B99791C@home.com \
--to=ischis2@home.com \
--cc=dj@redhat.com \
--cc=gdb@sourceware.cygnus.com \
--cc=kevinb@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