-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relocation "_cinit" #3
Comments
Hi ..... |
It seems this is a problem caused by sdcc. _cinit looks like referring to its C library. Looking at usin the C library: When telling sdcc to use crt0.o, it also builds without errors
Also this runs fine. Nevertheless, I believe this problem should be reported upstream at sdcc, as it doesn't select a valid c runtime by default. |
Hi Im new to sdcc in part although I have used older versions I tried the Ubuntu package which supposedly installs SDCC ver 3.4 together with gputils which should both work together having not had a problem with previous version but on a 32 bit ubuntu platform I then uninstall these due to the fact that no pic libraries were present on this and to find that despite instructions left in the folders to compile these libraries there is no configure,in as suggested for doing this There after i decided to use sourceforge for downloads gputils and of course sdcc Version being used is as follows for SDCC sdcc --version gpasm version This is the file Im compiling in C using sdcc #include <pic14/pic12f675.h> //Use this configuration word: __code int __at(_CONFIG) __CONFIG = 0x31c4; //Setup variables void main(void)
} This is the make file CC=sdcc all: $(SRC:.c=.hex)
clean: .PHONY: all clean Finally a similar problem in retrospect to others who have commented on this issue after compiling make I'm attaching the hex and asm files for viewing as well
sharebank udata_ovr 0x0020 ;-------------------------------------------------------- ID_blink_led_0 idata ID_blink_led_1 idata ;-------------------------------------------------------- ; code size estimation:
Below the hex file :1000000000000228E830AE000030AF008030000071 Any ideas at all on this or why this might be Ive searched high and low for answers on the net Id really appreciate any help or suggestions that some one might be able to offer bearing in mind I dont know to much about sdcc at all Thanking you Mark Harrington |
The PIC14 and PIC16 builds on SDCC have multiple problems. Some of them, including this one, seems to be caused by a problem in SDCC's build system. For example, I can see the same problem when SDCC is built manually on Debian Sid, but the official Linux build "sdcc-snapshot-amd64-unknown-linux2.5" doesn't have this problem at all. The Windows build is probably broken due to the same reason. The upstream source needs some serious troubleshooting. |
I would also like to see this back up and running I think I have only ever managed to get this to work all of three times to some part with old disto's of Linux Terrible shame as this would be very good for many people especially with view to how much you now pay for MPlabx full versions in terms of what they want and how much control they exert over many which none of us agree with |
Everytime I compile the program (7 segment). I get this message
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0000] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0004] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x001E] has no section. (pass 0)
warning: Relocation symbol "_cinit" [0x0022] has no section. (pass 0)
I use windows 8.1 and I've installed gputils.Is this a bug or is my system causing this troble?????
The text was updated successfully, but these errors were encountered: