From: Daniel Jacobowitz <drow@mvista.com>
To: David Jones <davidjones_home@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver error (getprotobyname)
Date: Thu, 14 Feb 2002 06:30:00 -0000 [thread overview]
Message-ID: <20020214093042.A31425@nevyn.them.org> (raw)
In-Reply-To: <20020214070702.5676.qmail@web13706.mail.yahoo.com>
On Wed, Feb 13, 2002 at 11:07:02PM -0800, David Jones wrote:
>
> Hi All,
> Thanks for the comments and suggestions to my gdbserver problem.
>
> > > The /etc/protocols file is present on my StrongArm target.
> >
> > Are /etc/nsswitch.conf and /lib/libnss_files* and friends?
> >
> > But in any case I recommend Martin's patch.
> >
>
> Daniel,
> I don't have /etc/nsswitch.conf and /lib/libnss_files* and friends
> since I used a statically linked binary for the StrongArm given to me
> by Bill. I will check out the gdb source, apply Martin's patch, and
> try to build gdb and gdbserver from the source. One question though,
> are there any special or unique options that I need to pass to the configure
> script ?
No, the files I was referring to are all parts of the C library. If
you left them out, get*byname will not work on your target.
If you check out the CVS repository, you should need no special
options. Be sure to build a -native-, not cross, gdb: --host=arm-linux
rather than --target=arm-linux.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-02-14 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 22:40 David Jones
2002-02-12 23:10 ` Martin M. Hunt
2002-02-12 23:25 ` Daniel Jacobowitz
2002-02-13 7:13 ` Daniel Jacobowitz
2002-02-13 23:07 ` David Jones
2002-02-14 6:30 ` Daniel Jacobowitz [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=20020214093042.A31425@nevyn.them.org \
--to=drow@mvista.com \
--cc=davidjones_home@yahoo.com \
--cc=gdb@sources.redhat.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