From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [patch] Add ser-tcp.o to all NetBSD host Makefile fragments
Date: Fri, 04 Jan 2002 15:15:00 -0000 [thread overview]
Message-ID: <20020104151526.G9599@dr-evil.shagadelic.org> (raw)
In-Reply-To: <3C3631B7.9080500@cygnus.com>; from ac131313@cygnus.com on Fri, Jan 04, 2002 at 05:50:31PM -0500
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
On Fri, Jan 04, 2002 at 05:50:31PM -0500, Andrew Cagney wrote:
> Dig dig. Hmm, have a look at what configure.in does with SER_HARDWIRE.
> Looks like the file needing a fix is config/arm/nbsd.mh.
Aha, I see. Ok.
> As a rule of thumb, a host specific file should set off an alarm bell -
> host specific stuff is (in theory ...) all handled by autoconf.
Then this patch ought to do the trick.
[ for gdb/ChangeLog ]
2002-01-04 Jason Thorpe <thorpej@wasabisystems.com>
* config/arm/nbsd.mh (XDEPFILES): Remove ser-tcp.o.
> PS: Why delete the comment.
Consistency with the others, mostly.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
[-- Attachment #2: patch1 --]
[-- Type: text/plain, Size: 620 bytes --]
Index: config/arm/nbsd.mh
===================================================================
RCS file: /cvs/src/src/gdb/config/arm/nbsd.mh,v
retrieving revision 1.2
diff -c -r1.2 nbsd.mh
*** nbsd.mh 2001/12/17 21:14:10 1.2
--- nbsd.mh 2002/01/04 23:10:55
***************
*** 1,5 ****
# Host ARM running NetBSD
! XDEPFILES= ser-tcp.o
NATDEPFILES= fork-child.o infptrace.o inftarg.o corelow.o armnbsd-nat.o
XM_FILE=xm-nbsd.h
NAT_FILE=nm-nbsd.h
--- 1,5 ----
# Host ARM running NetBSD
! XDEPFILES=
NATDEPFILES= fork-child.o infptrace.o inftarg.o corelow.o armnbsd-nat.o
XM_FILE=xm-nbsd.h
NAT_FILE=nm-nbsd.h
next prev parent reply other threads:[~2002-01-04 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 14:14 Jason R Thorpe
2002-01-04 14:50 ` Andrew Cagney
2002-01-04 15:15 ` Jason R Thorpe [this message]
2002-01-04 15:32 ` Andrew Cagney
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=20020104151526.G9599@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@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