Mercurial > hg > index.cgi
comparison extra/README @ 182:e0cc66fd0551
Added gcc6809lw patch to extras
author | lost@l-w.ca |
---|---|
date | Wed, 21 Sep 2011 21:14:09 -0600 |
parents | 84eb35251849 |
children | 83bb31ca8b6a |
comparison
equal
deleted
inserted
replaced
181:5350ce9f446f | 182:e0cc66fd0551 |
---|---|
2 purposes. | 2 purposes. |
3 | 3 |
4 as | 4 as |
5 | 5 |
6 This is a sort of front-end script that makes lwasm look approximately like | 6 This is a sort of front-end script that makes lwasm look approximately like |
7 gnu as which is useful for using lwasm as a backend to gcc. You will | 7 gnu as which is useful for using lwasm as a backend to gcc. You may need to |
8 probably need to edit it to make it work fully. Simply put this in place | 8 edit it to make it work fully. |
9 of whatever gcc6809 installed for "as" (in the "m6809/bin" folder in | |
10 "--prefix") after editing it to point to the real location of the "lwasm" | |
11 binary. | |
12 | |
13 | 9 |
14 ld | 10 ld |
15 | 11 |
16 Similar to the "as" script above except for lwlink. | 12 Similar to the "as" script above except for lwlink. |
17 | 13 |
18 | 14 |
19 ar | 15 ar |
20 | 16 |
21 Similar to the "as" script above except for lwar. | 17 Similar to the "as" script above except for lwar. |
22 | 18 |
19 gcc6809lw-4.6.1-1.patch | |
20 | |
21 These are patches to the main gcc source distribution for specific releases. | |
22 The last number after the dash is a patch level for the specific patch. | |
23 These are different to the official gcc6809 releases in the following ways. | |
24 First, all the source for as-6809 is removed. Also, the special "helper" | |
25 makefile and directory is removed. Also, as of this writing, the | |
26 distribution side for gcc6809 has been down for months and the latest | |
27 release was for gcc 4.3.4 which does not build on 64 bit linux. | |
28 | |
23 | 29 |
24 To use these scripts, you really need to understand how to build a gcc as a | 30 To use these scripts, you really need to understand how to build a gcc as a |
25 cross compiler. The basics are that you put the as, ld, and ar scripts | 31 cross compiler. The basics are that you put the as, ld, and ar scripts |
26 whereever you plan to put your cross-development binaries. Then, when | 32 whereever you plan to put your cross-development binaries. Then, when |
27 building the cross compiler, you tell it where the scripts are. | 33 building the cross compiler, you tell it where the scripts are. |
28 | 34 |
29 The following worked with gcc6809 4.3.4-3: | 35 The following work |
30 | 36 |
31 1. Install the ar, as, and ld scripts named m6809-unknown-{as,ar,ld} in a | 37 1. Install the ar, as, and ld scripts named m6809-unknown-{as,ar,ld} in a |
32 directory in your path, say /usr/local/coco/bin/. | 38 directory in your path, say /usr/local/coco/bin/. |
33 | 39 |
34 2. Make symbolic links to /bin/true for similarly named nm, objdump, ranlib, | 40 2. Make symbolic links to /bin/true for similarly named nm, objdump, ranlib, |
35 and strip in the same directory Some of these may not be necessary. | 41 and strip in the same directory Some of these may not be necessary. |
36 | 42 |
37 3. Unpack gcc and apply the gcc6809 patch. | 43 3. Unpack gcc and apply the gcc6809 patch. The gcc6809lw* patch file |
44 in this directory is known to work with these instructions. | |
38 | 45 |
39 4. Make sure /usr/local/coco/bin is in your PATH | 46 4. Make sure /usr/local/coco/bin is in your PATH |
40 | 47 |
41 5. Make sure "." is NOT in your path or is at the END of PATH. If you have | 48 5. Make sure "." is NOT in your path or is at the END of PATH. If you have |
42 gazillions of errors pop up compiling "gemodes.c", this is your problem. | 49 gazillions of errors pop up compiling "gemodes.c", this is your problem. |