>> build.sh -a powerpc -d -m macppc -D /home/mouse/macppc -O /home/mouse/macppc/.obj -U
> As a note, build.sh does a simple lookup to get '-a powerpc' if you
> just specify '-m macppc', so the -a is redundant.

Ah, yes, on reading build.sh I see what you mean.

> I've been using a command like this, specifying -T and not -O.  I
> haven't had any problems like these.  Do you have any tool-related
> environment variables or variables set in /etc/mk.conf?

No.  /etc/mk.conf does not even exist.

I did some more groveling around, and it seems that build.sh does not
get along well with having . early in your path.  I've artificially
removed . from the path entirely and it's now ticking along, well past
the previous point of failure.

ISTM that it should either work anyway (by providing its own path
setting, maybe?) or produce a comprehensible complaint.  Spuriously
running the cross-as instead of the host-as as assembler seems, shall
we say, suboptimal.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B