Fixed order of -o and -t on the linker command line.

git-svn-id: svn://svn.cc65.org/cc65/trunk@4886 b7a2c559-68d2-44c3-8de9-860c34a00d81

doc/cl65.sgml

@@ -245,7 +245,7 @@ into an executable named morse:
 	cc65 -g -Oi -t c64 morse.c
 	ca65 -g morse.s
 	ca65 -g irq.s
-	ld65 -t c64 -o morse c64.o morse.o irq.o c64.lib
+	ld65 -o morse -t c64 c64.o morse.o irq.o c64.lib
 </verb></tscreen>
 
 When using cl65, this is simplified to

doc/debugging.sgml

@@ -45,7 +45,7 @@ arbitary addresses), debug interrupt handlers and even debug routines that run
 inside the 1541 floppy.
 
 <item>You may use the label file generated by the linker to make much more use
-from the monitor.     
+from the monitor.
 
 </itemize>
 
@@ -90,7 +90,7 @@ file (I'm usually using a <tt/.lbl/ extension for these files). An example for
 a linker command line would be:
 
 <tscreen><verb>
-    ld65 -t c64 -Ln hello.lbl -m hello.map -o hello crt0 hello.o c64.lib
+    ld65 -o hello -t c64 -Ln hello.lbl -m hello.map hello.o c64.lib
 </verb></tscreen>
 
 This will generate a file named hello.lbl that contains all symbols used in

doc/grc65.sgml

@@ -241,7 +241,7 @@ contains all of the executable code.
 
 <sect2>Fourth and last step -- linking it together
 <p><verb>
-$ ld65 -t geos -o test.cvt resource.o geos.o test.o geos.lib
+$ ld65 -o test.cvt -t geos resource.o geos.o test.o geos.lib
 </verb>
 &dquot;<tt/resource.o/&dquot; comes first because it contains the
 header.  The next one is &dquot;<tt/geos.o/&dquot;, a required starter-code

doc/intro.sgml

@@ -185,7 +185,7 @@ linker can resolve those functions.
 Let's link our files to get the final executable:
 
 <tscreen><verb>
-        ld65 -t c64 -o hello hello.o text.o c64.lib
+        ld65 -o hello -t c64 hello.o text.o c64.lib
 </verb></tscreen>
 
 The argument after <tt/-o/ specifies the name of the output file, the argument