2013/12/11 IorićYONEJI <[email protected]>: > Hi, > > Which compiler name is preferable "or32-*-*", or "or1k-*-*"? > I thought or1k-*-*- is newer one and default settings should use newer > one, so I made small patch. This patch fixes sw/Makefile.inc in > official svn orpsocv2 repository (not v3). > > And I found more name of "or32-" in the v2 repo, but I don't know > whether I should send you a patch to fix them all, so I send you this > patch to fix just one. > Below is the list what or32- is. > > doc/orpsoc.texi:Create the executable for the program you wish to boot > out of flash. Generate a binary of it using @code{or32-elf-objcopy} > like so: > doc/orpsoc.texi:@kbd{or32-elf-objcopy -O binary @emph{yourexe.elf} > @emph{youroutputfile.bin}} > sim/bin/Makefile:ARCH_SIM_EXE ?=or32-elf-sim > sw/utils/Makefile:all: $(PROGRAMS) or32-idecode > sw/utils/Makefile:.PHONY or32-idecode: > sw/utils/Makefile:or32-idecode: > sw/utils/Makefile: $(MAKE) -C or32-idecode > sw/utils/Makefile: $(MAKE) -C ./or32-idecode clean > sw/utils/or32-idecode/Makefile:APP=or32-idecode > sw/utils/or32-idecode/Makefile:all: or32-opc.o or32-dis.o > sw/utils/or32-idecode/or32-dis.c:// Simple program to do disassembly > like or32-objdump but on individual instructions passed to it > sw/apps/spiflash/README:$ or32-elf-objcopy -O binary myapp.elf myapp.bin > > Finally, below is the patch. > > Index: sw/Makefile.inc > =================================================================== > --- sw/Makefile.inc (revision 865) > +++ sw/Makefile.inc (working copy) > @@ -29,7 +29,7 @@ > #### #### > ###################################################################### > > -OR32_TOOL_PREFIX=or32-elf- > +OR32_TOOL_PREFIX=or1k-elf- > > OR32_LD=$(OR32_TOOL_PREFIX)ld > OR32_AS=$(OR32_TOOL_PREFIX)as > _______________________________________________ > Openrisc mailing list > [email protected] > http://lists.opencores.org/listinfo/openrisc
Hi Iori, Thanks for the patch. We like users that scratch their own itches :) I have hit the same problem trying to build orpsocv2 with the or1k- toolchain. I'm not sure if this is the right way to do it however. There are two reasons for this: 1. If we change that, we might get angry complaints from the or32- users. Another way to do it might be to make it possible to overrride OR32_TOOL_PREFIX (like OR32_TOOL_PREFIX ?=or32-elf-). 2. Are you sure that this is enough. IIRC it still failed because the linker scripts were set to the wrong architecture, and I couldn't figure out how to override that without some sed hacking. With that being said, I don't really have any strong opinions on the matter, so I'm leaving it up to someone else to ack or nack the patch Regards, Olof _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
