From: Andrew Cagney <ac131313@cygnus.com>
To: thorpej@wasabisystems.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 14:50:00 -0000 [thread overview]
Message-ID: <3C3631B7.9080500@cygnus.com> (raw)
In-Reply-To: <20020104141453.E9599@dr-evil.shagadelic.org>
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.
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.
enjoy,
Andrew
PS: Why delete the comment.
> Index: config/i386/nbsd.mh
> ===================================================================
> RCS file: /cvs/src/src/gdb/config/i386/nbsd.mh,v
> retrieving revision 1.10
> diff -c -r1.10 nbsd.mh
> *** nbsd.mh 2001/10/02 23:11:21 1.10
> --- nbsd.mh 2002/01/04 21:56:51
> ***************
> *** 1,13 ****
> # Host: Intel 386 running NetBSD
> ! XDEPFILES=
> !
> ! # NATDEPFILES must remain entirely on one line for *BSD. When
> ! # building a cross debugger, configure will cause this line to be
> ! # commented out in the Makefile. BSD make doesn't permit the use of a
> ! # continuation character (backslash) to extend a commented line. As a
> ! # consequence, BSD make considers subsequent tab-indented lines to be
> ! # "unassociated shell commands".
> NATDEPFILES= fork-child.o infptrace.o inftarg.o corelow.o i386nbsd-nat.o solib.o solib-sunos.o
> -
> XM_FILE= xm-nbsd.h
> NAT_FILE= nm-nbsd.h
> --- 1,5 ----
> # Host: Intel 386 running NetBSD
> ! XDEPFILES= ser-tcp.o
> NATDEPFILES= fork-child.o infptrace.o inftarg.o corelow.o i386nbsd-nat.o solib.o solib-sunos.o
> XM_FILE= xm-nbsd.h
> NAT_FILE= nm-nbsd.h
>
next prev parent reply other threads:[~2002-01-04 22:50 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 [this message]
2002-01-04 15:15 ` Jason R Thorpe
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=3C3631B7.9080500@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=thorpej@wasabisystems.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