From: <eur...@ao...> - 2007-04-29 20:54:11
|
SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0 #4309 (Jul 28 2006) (UNIX) using mac osx oh, as for the apostrophe topic: the .c file is this: #include <string.h> char str1[10]; void main(void) { strcpy(str1, "testing"); } i dont see any apostrophes, isn't this (') what would make sense as producing that error.. i understand i am still a little unfamiliar with some syntaxes, dont know what the apostrophes is about. i then did the snapshot suggestion in terminal: COMPUTER:~ myname$ cd ~/FOLDER/FOLDER/ COMPUTER:~/FOLDER/FOLDER myname$ ~/FOLDER/FOLDER/sdcc/bin/sdcc test.c test.c:24:10: warning: backslash-newline at end of file test.c:1: warning 190: ISO C forbids an empty source file test.c:1: parse error: token -> '{' ; column 1 ok bros, even afterwards, i opened the test.c and it had text in it ("ISO C forbids an empty source file"), if ur guys' compilers are working, there must be some solution.. i think i provided all the relevant information i can, if there's anything else i can tell you, i will. oh, i have xcode on the computer, (installed it after the first version of sdcc, before the snap version), i installed it to compile glut as recommended by the mac dev site. bye |
From: <eur...@ao...> - 2007-04-30 03:16:14
|
hi COMPUTER:~/FOLDER/FOLDER myname$ ~/FOLDER/FOLDER/sdcc/bin/sdcc -E test.c # 1 "test.c" # 1 "<built-in>" # 1 "<command line>" # 1 "test.c" {\rtf1\mac\ansicpg10000\cocoartf102 {\fonttbl\f0\fmodern\fcharset77 Courier;\f1\froman\fcharset77 Times-Roman;} {\colortbl;\red255\green255\blue255;} \margl1440\margr1440\vieww9000\viewh9000\viewkind0 \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx560 0\tx6160\tx6720\ql\qnatural \cf0 \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx560 0\tx6160\tx6720\ql\qnatural \f0\fs26 \cf0 #include <string.h> \f1\fs32 \'ca \'ca \f0\fs26 char str1[10]; \f1\fs32 \'ca \'ca \f0\fs26 void main(void) \{ \f1\fs32 \'ca \f0\fs26 \'ca\'castrcpy(str1, "testing"); \f1\fs32 \'ca \f0\fs26 \} test.c:24:10: warning: backslash-newline at end of file \f1\fs32 } -- and for the include thing: COMPUTER:~/FOLDER/FOLDER myname$ ~/FOLDER/FOLDER/sdcc/bin/sdcc -I ~/FOLDER/FOLDER/sdcc/share/sdcc/include test.c test.c:24:10: warning: backslash-newline at end of file test.c:1: warning 190: ISO C forbids an empty source file test.c:1: parse error: token -> '{' ; column 1 i'm thinking if there are any ways that I can try to resolve this ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com. |
From: Dave M. <mc...@ne...> - 2007-04-30 03:26:54
|
On Apr 29, 2007, at 11:15 PM, eur...@ao... wrote: > COMPUTER:~/FOLDER/FOLDER myname$ ~/FOLDER/FOLDER/sdcc/bin/sdcc -E > test.c > # 1 "test.c" > # 1 "<built-in>" > # 1 "<command line>" > # 1 "test.c" > {\rtf1\mac\ansicpg10000\cocoartf102 > {\fonttbl\f0\fmodern\fcharset77 Courier;\f1\froman\fcharset77 > Times-Roman;} .... > i'm thinking if there are any ways that I can try to resolve this Ahh, it looks like you're trying to compile an RTF file, not C source code. Did you create this with TextEdit or something similar? If so...get thyself a programming editor that will deal with files as plain text. Until you find one that you like, tell TextEdit to save your file as plain text. -Dave -- Dave McGuire Port Charlotte, FL |
From: <eur...@ao...> - 2007-04-30 05:35:18
|
oh my g-d i'm w/o words now i've tried changing the format and the apostrophe thing went away (did that with ms-word), now im going for a programming editor (have vim, etc in mind) your comment has eased all this trouble, later -----Original Message----- From: mc...@ne... To: sdc...@li... Sent: Sun, 29 Apr 2007 11:27 PM Subject: Re: [Sdcc-user] con't compiler topic info On Apr 29, 2007, at 11:15 PM, eur...@ao... wrote: > COMPUTER:~/FOLDER/FOLDER myname$ ~/FOLDER/FOLDER/sdcc/bin/sdcc -E > test.c > # 1 "test.c" > # 1 "<built-in>" > # 1 "<command line>" > # 1 "test.c" > {\rtf1\mac\ansicpg10000\cocoartf102 > {\fonttbl\f0\fmodern\fcharset77 Courier;\f1\froman\fcharset77 > Times-Roman;} .... > i'm thinking if there are any ways that I can try to resolve this Ahh, it looks like you're trying to compile an RTF file, not C source code. Did you create this with TextEdit or something similar? If so...get thyself a programming editor that will deal with files as plain text. Until you find one that you like, tell TextEdit to save your file as plain text. -Dave -- Dave McGuire Port Charlotte, FL ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Sdcc-user mailing list Sdc...@li... https://lists.sourceforge.net/lists/listinfo/sdcc-user ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com. |
From: Frieder F. <fri...@we...> - 2007-04-29 21:34:10
|
Hi europa989, eur...@ao... schrieb: > SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.6.0 #4309 (Jul 28 2006) (UNIX) > > using mac osx thanks! > oh, as for the apostrophe topic: > the .c file is this: > > #include <string.h> > > char str1[10]; > > void main(void) { > strcpy(str1, "testing"); > } > > i dont see any apostrophes, isn't this (') what would make sense as producing that error.. I did not see any apostrophes either:) - Yet SDCC issues: /Users/name/test.c:10:11: missing terminating ' character (citing the first error message from your todays original post: [Sdcc-user] hi compile errors for newb) this means there is (or SDCC sees) a problem in test.c line 10 column 11. Which is strange as the source (which compiles fine here on SDCC 2.6.5 #4781 on OpenSUSE 10.2)) has less than 10 lines. That made me think that there might be additional comment lines above the source you provided. (which might contain text with "it's", "can't", "isn't", "won't") Can we make certain by f.e. passing the problematic source to a checksum utility (md5sum, sha1sum, sha256sum) and appending the snippet to this mail that we are talking about the same code? Greetings, Frieder |
From: Raphael N. <rn...@we...> - 2007-04-29 23:09:51
|
Hi, >> #include <string.h> >> >> char str1[10]; >> >> void main(void) { >> strcpy(str1, "testing"); >> } > Can we make certain by f.e. passing the problematic source > to a checksum utility (md5sum, sha1sum, sha256sum) > and appending the snippet to this mail that we are talking > about the same code? Proposal: Check sdcc -E test.c on your box and post the longish output (reveals names/content of included files, possibly also path names...). I guess SDCC reads include files it should better not have seen (i.e. system include files from /usr/include and stuff. Even better, try sdcc -I /path/to/sdcc/include test.c to prevent SDCC from guessing about its include files (string.h must reside in /path/to/sdcc/include, obviously...). HTH, Raphael |