On Mon, 11 Jun 2012, it would appear that Raphael Neider wrote:
> Hi,
>
>> I'm new to sdcc, and am having some issues getting some very simple
>> code to compile for a pic processor on a Fedora 15 system. I'm running
>> with a clean build from a fresh checkout of the sdcc source from trunk.
>>
>>> sdcc -v
>> SDCC :
>> mcs51/gbz80/z80/z180/r2k/r3ka/ds390/pic16/pic14/TININative/ds400/hc08/s08
>> 3.1.5 #7876 (Jun 8 2012) (Linux)
>>
>> compiling what is essentially an 8 line program with:
>>> sdcc --debug -mpic14 -p12f675 toggle.c
>>
>> I'm getting a whole string of warnings such as:
>> /usr/local/bin/../share/sdcc/include/pic/pic12f675.h:64: warning 115:
>> unknown or unsupported #pragma directive 'memmap INDF_ADDR INDF_ADDR SFR
>> 0x000'
>
> pic12f675.h as currently distributed does not contain any #pragma
> lines. Are you sure you actually use your newly built sdcc ('which
> sdcc' might tell you that you actually use /usr/local/bin/sdcc instead
> of /home/login/bin/sdcc or wherever you installed your built sdcc). I
> guess that Fedora comes with some ancient (?) sdcc installed via the
> package manager, which now causes confusion.
> Please ./configure --prefix=$HOME/local sdcc, make && make install it,
> export PATH=$HOME/local/bin:$PATH, purge the shell's cache using 'hash
> -r' and try again. You might also pass
> -I/path/to/non-free/include/pic14 to force the compiler to look there
> first.
>
> The other errors seem to be follow-ups.
>
>> I've rebuilt the .c and .h files with inc2h.pl, and was seeing the same
>
> This procedure is not really recommended (nor usually required) for users ...
>
>> warnings when I ran with sdcc installed from a binary using yum.
>
> Ah, interesting. So there is / was an sdcc installed via yum. Please
> uninstall and try again.
>
>> Is the pic support really not ready to go yet, or is there something
>> else going on here?
>
> The PIC backends are usually useable, though they are not as mature as
> most other backends.
>
> Best regards
> Raphael
Raphael-
I rebuilt sdcc as you suggested, and running it with the
-I<path to include> seems to compile ok. I added -L<path to libs>
and it looks everything got generated. I'll dump the hex file to
make sure it's what I expect, but it looks good now.
Thanks for your help.
Joel
--
Joel Davidson
Austin, TX
j...@prismnet.com
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
