"Gilad Rom" <gilad@romat.com> writes:
> Yeah, everything besides the compiler runs fine. 

Doesn't mean much -- the compiler tends to hit the machine harder than
most stuff.

> I wouldn't mind about the compiler, but cross compiling
> anything other than the NetBSD userland/kernel
> seems to generate binaries that are not interperted the right
> way by the target board (Spews out something about "(" Unexpected).

That sounds wrong. It *should* work, but...

> So, any other way you guys know of cross compiling pkgsrc tools?

That's an entirely different kettle of fish -- most pkgsrc stuff isn't
set up to cross compile. You have to manually tweak all the makefiles
etc. to make it work.

Perry

>
> Thanks!
>
> ----- Original Message ----- 
> From: "Perry E.Metzger" <perry@piermont.com>
> To: "Gilad Rom" <gilad@romat.com>
> Cc: <port-evbmips@netbsd.org>
> Sent: Sunday, November 09, 2003 2:25 PM
> Subject: Re: mips compiler error?
>
>
>> 
>> "Gilad Rom" <gilad@romat.com> writes:
>> > I have successfully cross-built NetBSD using the build.sh script
>> > for my target board, which features the AMD Au1100 MIPS CPU.
>> >
>> > Now, when I try compiling anything bigger than "Hello, World!" on
>> > my target board, I get an internal compiler error, and a segmentation
>> > fault (The line number in the source file seems to be a random one).
>> >
>> > Is it even possible to run GCC on that board, or am I simply
>> > trying in vain?
>> 
>> Sounds like either a hardware problem, or an OS bug. Certainly there
>> is no theoretical reason why you should not be able to compile on the
>> board if you can cross compile for it.
>> 
>> Perry
>> 
>

-- 
Perry E. Metzger		perry@piermont.com