public inbox for
 help / color / mirror / Atom feed
* Re: Realure to build uberbaum tree for m68k-elf
       [not found]   ` <>
@ 2003-02-03 16:08     ` Christopher Faylor
  0 siblings, 0 replies; only message in thread
From: Christopher Faylor @ 2003-02-03 16:08 UTC (permalink / raw)
  To: Peter Barada; +Cc: peter, gcc, rda

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.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-02-03 16:08 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
2003-02-03 16:08     ` Realure to build uberbaum tree for m68k-elf Christopher Faylor

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).