Subject: Bizzar XCompiling problem
To: None <current-users@NetBSD.ORG>
From: Bill Studenmund <skippy@macro.stanford.edu>
List: current-users
Date: 12/06/1997 13:38:36
Howdy!

I'm trying to get my X86 set up to xcompile to my mac.

The only problem I'm running into involves libkern (at present). For some
reason, the silly computer tries to make .o.o files out of some of the
/sys/lib/libkern files.

Yes, .o.o files.

So far, it's tried it for __assert.c, dvidi3.c, moddi3.c, qdivrem.c,
udivdi3.c, umoddi3.c, and md5.c.

For these files, the compile message on the screen looks fine
(/usr/lcoal/bin/m68k-netbsd-gcc <all the flags> -c
/src/sys/lib/libkern/<name>.c) but then m68k-netbsd-ld complains that
<name>.o.o has a relocation symbol number out of range.

If I suspend the compile just as it's starting this step, I see that sh is
forking gcc as shown above, but with -c <name>.o.o on the end.

If, however, I cd to /sys/arch/mac68k/compile/KERNEL/lib/kern and execute
the command directly, then I get a good <name>.o file.

I've got the lates mk files, and am running a make from Nov. 15. Any idea
what's wrong?

Take care,

Bill