From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <507def6adc5ca165a284c7be81a66605@chula.quanstro.net> References: <4F171398.8020701@Princeton.EDU> <4F1D1C4F.4040003@gmail.com> <507def6adc5ca165a284c7be81a66605@chula.quanstro.net> From: Jens Staal Date: Tue, 24 Jan 2012 05:43:33 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] ape compiler error, IND CHAR and INT Topicbox-Message-UUID: 610ef6fa-ead7-11e9-9d60-3106f5b1d025 Thanks for the feedback! The dlerror was indeed the culprit and now my errors have jumped to: " syntax error, last name: 0 pcc: cpp: 469: error " , presumably in the generated .c file. Where can I find info about the "469" error and how do I know where the error occurred? (previously I have had more informative "last names" to jump to...) I also added the "-+" to CFLAGS. I have no idea if this may help with the problems with // comments. 2012/1/23 erik quanstrom : >> The line number is off-by-one, for some reason, but since the operation is >> AS (assign), and since the assignment from dlerror is on the next line, and >> dlerror won't be declared anywhere, that's most likely to be the problem. > > i think the compiler eats the newline sometimes when there's a // comment > on a preprocessor line. > > i thought i submitted a fix for this. > > - erik > >