Thank you for your help. I had not included -p18f47j53 because the code has a "#define __18f47j53" statement, and sdcc complained about it being defined twice (I guess now I should do it the other way around, remove the #define and leave it on the command line to make the option available to the linker too).
I could not find anything related to crt0 or any of the gputils in config.log. I've run again ./configure and make and all I found is gputils checks which look ok, as in (./configure output): checking for gpasm... /usr/bin/gpasm checking for gplink... /usr/bin/gplink checking for gplib... /usr/bin/gplib checking for style of include used by make... GNU checking dependency style of '/home/luis/sdcc/sdcc/device/lib/pic14//../../../bin/sdcc'... none checking dependency style of '/usr/bin/gpasm'... none I did the build process with the normal commands (./configure make and make install), with gputils 0.13.7 being installed from the ubuntu repository. The gpasm version I have does not support 18f47j53 actually. (note it supports 18f452 !). Here is the output for the command, including the -p18f47j53 option as Raphael suggested and removing the #define I mentioned before toggle_led.asm:8:Error [132] Unknown processor. toggle_led.asm:10:Error [131] Processor type is undefined. toggle_led.asm:548:Error [131] Processor type is undefined. toggle_led.asm:549:Error [131] Processor type is undefined. toggle_led.asm:552:Error [131] Processor type is undefined. toggle_led.asm:553:Error [131] Processor type is undefined. toggle_led.asm:554:Error [131] Processor type is undefined. I guess that is probably related to gpasm version not dealing with 18f47j53. Just in case, there are other pic18fxxxx.lib files which built succesfully in the sdcc tree. I will try to investigate it a bit more, starting from "The mess with new devices in the pic ports" Philipp suggested, and trying to read the logs slowly to understand what happened. Thanks! Luis On Fri, Feb 15, 2013 at 10:01 AM, Philipp Klaus Krause <p...@spth.de> wrote: > On 14.02.2013 23:12, Raphael Neider wrote: > >> >> Can you verify that your sdcc build passed cleanly? I assume that >> gputils were not found when you built sdcc, so no libraries nor >> crt*.o files could be built. While this is strange, as the build >> system used to bail out with an error in that situation, you may >> have tricked it somehow into continuing (different PATH at >> configure time vs make time? make -k?). >> >> crt0i.o should never be missing, unless the build/install did not >> succeed properly. > > Silent failure to build any PIC libraries is the normal sdcc behaviour > when the installed gputils version does not support all devices > supported by sdcc. Since gputils in distributions tends to be older, > this is what practically everyone building sdcc from source will > experience, unless they know that a recent gputils is required. > > Philipp > > P.S.: See also my message "The mess with new devices in the pic ports" > to sdcc-devel from last November. > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Sdcc-user mailing list > Sdcc-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sdcc-user ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
