public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] Re: Question about cross-compile builds failing
       [not found] <1E7A4807A136DF45AD33DB341D93C3BD56B018@msgswbmnmsp46.wellsfargo.com>
@ 2008-03-31  2:34 ` Andrew Lunn
  0 siblings, 0 replies; only message in thread
From: Andrew Lunn @ 2008-03-31  2:34 UTC (permalink / raw)
  To: Greg.Chandler; +Cc: eCos Disuss

On Sat, Mar 29, 2008 at 02:04:16AM -0500, Greg.Chandler@wellsfargo.com wrote:

ecos-discuss is a better place to discuss issues like this.

> 
> I've got a system that I am doing builds on so that I can get an PXA-255
> based system up and running.  It's x86_64.  My cross-compiler works, and
> I have booted ARM kernels that it has built.  I'm using the ARM-tree
> maintained by Russell King.
> 
> Since this isn't a native system, and not the same tree as the running
> kernel the headers do not live /usr/include/.
> 
> The build seems to require this no matter what I set at the configure
> level.  Here's what the configure/make shows.  Am I doing something
> wrong or was it designed this way?  I've also tried undoing the defines
> for the USB since I really don't need it, but that didn't work for me
> either.

The eCos tools you are trying to build are used only on the host
system, not the target system. So you should be building x86_64 tools,
not arm tools.  

Or do you really want to build eCos using your ARM Linux system?

    Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

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

only message in thread, other threads:[~2008-03-29  8:35 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1E7A4807A136DF45AD33DB341D93C3BD56B018@msgswbmnmsp46.wellsfargo.com>
2008-03-31  2:34 ` [ECOS] Re: Question about cross-compile builds failing Andrew Lunn

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