From: Christopher Faylor <cgf@redhat.com>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: peter@baradas.org, gcc@gcc.gnu.org, rda@sources.redhat.com
Subject: Re: Realure to build uberbaum tree for m68k-elf
Date: Mon, 03 Feb 2003 16:08:00 -0000 [thread overview]
Message-ID: <20030203160857.GA11365@redhat.com> (raw)
In-Reply-To: <200302031604.h13G4HU26161@hyper.wm.sps.mot.com>
On Mon, Feb 03, 2003 at 11:04:17AM -0500, Peter Barada wrote:
>
>>>I haven't been ablke to build the uberbaum tree configured with
>>>--target=m68k-elf for the past few days. Previous I had problems with
>>>a missiung tk8.4 directory, and it was suggested by Christopher Faylor
>>>that I remove it. After removing the tix directory and configuring
>>>again, the build fails trying to build the rda part of GDB:
>>>
>>>/home/peter/work/cvs-gnu/uberbaum/rda/lib/gdbsocket.c: In function `gdbsocket_startup':
>>>/home/peter/work/cvs-gnu/uberbaum/rda/lib/gdbsocket.c:191: error: storage size of `sockaddr' isn't known
>>
>>Well, you can remove rda, too, unless you are going to be needing it,
>>which is unlikely.
>
>I thought someone would like to know that it doesn't build
>'out-of-the-box'. If I read rda/lib/gdbsocket.c correctly, I can't
>see how it can build for a embedded target that uses newlib since
>newlib doesn't supply a sockaddr_in definition.
>
>Would it be wrong to suggest that rda should not attempt to build
>itself for any target that requires newlib?
No, I don't think it's wrong. There have been some discussions in the rda
mailing list about this. I've cc'ed this message there.
cgf
parent reply other threads:[~2003-02-03 16:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200302031604.h13G4HU26161@hyper.wm.sps.mot.com>]
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=20030203160857.GA11365@redhat.com \
--to=cgf@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pbarada@mail.wm.sps.mot.com \
--cc=peter@baradas.org \
--cc=rda@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).