It would be useful to know the actual command that you entered...? I used something like this when I started off...
sdcc -mz80 test.c the -mz80 tells sdcc what the target machine CPU is and therefore fairly essential ;-) On Wednesday 04 March 2009 22:17:22 Matt Baker wrote: > Hi > I can't compile the test.c file following the instructions in the > documentations. > I am new to sdcc and Linux... > > Report is > sdcc: SDCCglue.c:1855: glue: Assertion `mcs51_like' failed. > Caught signal 6: SIGABRT > > I installed sdcc not built it from source. But I don't remember where I > downloaded it from. > *"sdcc --version *reports > SDCC : avr/pic16/pic14/xa51 2.8.0 #5117 (Jun 2 2008) (UNIX) > > FYI my background is electronics not computers. > > Matt Baker -- Richard. PGP Key-id: 0x5AB3D350 ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
