I'm attempting to synthesize orpsoc for the Xilinx ML501 board and have run into a few issues.

I checked out the orpsocv2 directory from the svn server and I'm attempting to run 'make all' in the orpsocv2/boards/xilinx/ml501/syn/xst/run directory. The following is the error I receive.

make all

#### Generating Xilinx PRJ file ####


#### Generating XST file ####


#### Generating Xilinx XCF file ####


### Generating bootup ROM ###

make[1]: Entering directory `/home/deowen/openrisc/orpsocv2/boards/xilinx/ml501/sw/bootrom'
make[2]: Entering directory `/home/deowen/openrisc/orpsocv2/sw/bootrom'

\t### Creating software defines header from verilog defines ###


\t### Creating OR1200 software defines header from verilog defines ###

bootrom.S: Assembler messages:
bootrom.S:147: Error: no such instruction: `l.movhi r0,0'
bootrom.S:148: Error: no such instruction: `l.movhi r4,0x0'
bootrom.S:149: Error: no such instruction: `l.ori r4,r4,0x100'
bootrom.S:150: Error: no such instruction: `l.jr r4'
bootrom.S:151: Error: no such instruction: `l.nop'
make[2]: *** [bootrom.o] Error 1
make[2]: Leaving directory `/home/deowen/openrisc/orpsocv2/sw/bootrom'
make[1]: *** [../../../../../sw/bootrom/bootrom.v] Error 2
make[1]: Leaving directory `/home/deowen/openrisc/orpsocv2/boards/xilinx/ml501/sw/bootrom'
make: *** [/home/deowen/openrisc/orpsocv2/boards/xilinx/ml501/syn/xst/run/../../../sw/bootrom/bootrom.v] Error 2

My initial thoughts are that my $PATH is possibly messed up and it's using the wrong compiler/assembler, but I've thoroughly debugged that and I'm sure my $PATH is correct. or32-elf-* and or32-linux* are both available in my $PATH.
My second thought is that maybe I checked out the wrong version of the orpsoc source. I spent a while trying to make sure I had the latest stable source, but the svn organization is so complex that I'm not entirely sure. If someone could affirm that I have the latest stable source or not I would appreciate that as well.

So, can anyone offer a suggestion?

Don

Resolved.

What went wrong ?

My $PATH *was* somewhat incorrectly configured. The issue is that, even though the correct or32- tools were in my path, they were at the end of my path and the tools were, for some reason, matching other gcc instances that were earlier in my path. I fixed it by putting the or32- tools at the beginning of my path. I also documented this here: http://opencores.org/or1k/OpenRISC_GNU_tool_chain#Installation_from_source