build status for cross builds?

Paul Koning pkoning@equallogic.com
Sat Jan 5 09:22:00 GMT 2002


Excerpt of message (sent 4 January 2002) by mike stump:
> > Date: Fri, 4 Jan 2002 17:26:41 -0500 (EST)
> > From: Paul Koning <pkoning@equallogic.com>
> > To: gcc@gcc.gnu.org
> 
> > A lot of these were recent, as I tried many variations to attempt
> > --target=mips-netbsd --with-newlib
> 
> I am sorry, netbsd doesn't use newlib, hence you loose.

Ah.  I don't know what gave me the idea that it did, or at least that
it supports that.  

The configure run didn't complain, as it does when you specify an
invalid target.  I assume that means simply that it doesn't check the
newlib switch...

I do know that we're using NetBSD as an embedded OS, with newlib, and
the code appears to be running, so the real answer may be a bit more
complex. 

It sounds like the thing to try is (a) build the toolset with glibc,
and (b) subsequently build newlib as a separate step using that
toolset.  Perhaps that will be easier to debug; in any case, it will
separate newlib related issues from gcc crossbuild issues.

Thanks...

	paul



More information about the Gcc mailing list