If that doesn’t help let me know, and I’ll look into it further.

Cheers,
Matt

just a troubleshot though, I can compile a test file on the command line without any options. but when I compile a project in piklab for a specific processor I’ve got the error you mentioned in the next step tutorial and tried to solved it as you said:

“pic30-coff-cc1: warning: Provide a resource file
pic30-coff-cc1: error: Invalid -mcpu option. CPU 30F4013 not recognized.
To solve this add -mresource=$C30INSTALL/info/c30_device.info to your GCC command line”

Well my problem is that I do not have this file in this directory, I just have:
cpp.info
cppinternals.info
dir
dir.old

could you tell me where to get this file or alternatively could you give it to me

many thanks,

William

PS: I had to ln -s the files to /usr/bin/ directory to make it visible for piklab.

I’ve added the find . -name “*.y” -o -name “*.l” -exec touch ‘{}’ line to the tutorial now. I spent the last few days puzzling over the Link Error problem and just as I was writing this comment remembered that someone else had previously posted a patch for it (it is due to integer sizes on 64bit machines.) I will update my patches, look for a new blog post today.

Cheers

I also had the “pic30-coff-ld:built in linker script:6: syntax error” error for a while, and can verify that the
“find . -name “*.y” -o -name “*.l” -exec touch ‘{}’ ‘;’” fix is necessary, and should probably be part of your setup steps for binutils. (especially if the comments box smart-formats the quotes!)

I’m trying to get it all working purely from the command line for the moment, so some other things took a while to figure out; for example “pic30-coff-ld: cannot find -lpic30-coff” errors are caused when you don’t have the “pic30-nonfree/lib” directory (copied from the academic/evaluation release) added to the libraries path, either globally through environment variables, or with a “-L{$C30INSTALL}/pic30-nonfree/lib”-ish parameter to GCC. (Obvious in retrospect, but not at the time.)

I also get “pic30-coff-gcc-4.0.3: installation problem, cannot exec ‘pic30-coff-as’: No such file or directory” errors (even though I’ve linked it from “libexec/gcc/pic30-coff/4.0.3/” as you suggest) unless I add the binaries directory to my $PATH.

I’m now onto more normal errors preventing simple test compiles, such as “Link Error: PC Relative branch to ‘.L2′ is out of range. Suggest large-code model.” (even though I’m setting “-mlarge-code”) which I hope will be solved by a more thorough read of the documentation, or providing explicit linker files. I hope.

I just wish Microchip allowed redistribution of binaries, to prevent others from having to go through this whole grinding, unforgiving process. This is the third time I’ve tried to build the toolchain, and my first actual success.

So it seems this process does work for v3.23, on a 64-bit Xeon SMP ‘Dreamhost’ web-hosting server account. I’m at least compiling .c to .o, even if I’m not linking properly yet.

Thanks!

ps: [three hours later] I still can’t get past the “Suggest large-code model.” error, even when compiling the MPLAB examples. I can get “output.s” to assemble to “output.o”, but the linker refuses to work. My current best try is “pic30-coff-ld -o output.cof output.o –script ../../support/dsPIC30F/gld/p30f3014.gld –heap=0 -L../../lib/dsPIC30F” but it always fails with the same problem:
output.o(.text+0×8):output.s: Link Error: PC Relative branch to ‘wait’ is out of range. Suggest large-code model.
output.o(.text+0xe):output.s: Link Error: PC Relative branch to ‘print_string’ is out of range. Suggest large-code model.
output.o(.text+0×20):output.s: Link Error: PC Relative branch to ‘print_string’ is out of range. Suggest large-code model.
output.o(.text+0×24):output.s: Link Error: PC Relative branch to ‘exit’ is out of range. Suggest large-code model.

Any ideas?

There was a bit of a delay between when I actually built the compiler and when I wrote the tutorial, and in that time I forgot about one of the files I had patched. It was config.gcc which is responsible for the program prefix (e.g. pic30-coff- or pic30- ). For some reason in the v3.20 sources they had hardcoded the prefix to pic30-. I have fixed this so that it will be pic30-coff- (or whatever binary type you choose). I have updated pic30-gcc-3.20.tar.bz2 with this patch now.

Cheers

Tried to compile a small testcase but gcc couldn’t find cc1 nor as :
“pic30-coff-gcc: installation problem, cannot exec ‘pic30-cc1′: No such file or directory” (same with pic30-as)
ln -s $C30INSTALL/libexec/gcc/pic30-coff/4.0.3/pic30-coff-cc1 $C30INSTALL/libexec/gcc/pic30-coff/4.0.3/pic30-cc1 (same for as) did the trick…

Let us know how it goes with v3.22.

Cheers,
Matt

Thanks

Billy