Mercurial > hg > index.cgi
comparison extra/README @ 72:84eb35251849
Added extra scripts that can be used to run gcc6809 with lwtools as its binutils
| author | lost@l-w.ca |
|---|---|
| date | Tue, 12 Apr 2011 14:16:36 -0600 |
| parents | |
| children | e0cc66fd0551 |
comparison
equal
deleted
inserted
replaced
| 71:6dafb4f0fa56 | 72:84eb35251849 |
|---|---|
| 1 These files are extra utility type scripts that can be used for various | |
| 2 purposes. | |
| 3 | |
| 4 as | |
| 5 | |
| 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 | |
| 8 probably need to edit it to make it work fully. Simply put this in place | |
| 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 | |
| 14 ld | |
| 15 | |
| 16 Similar to the "as" script above except for lwlink. | |
| 17 | |
| 18 | |
| 19 ar | |
| 20 | |
| 21 Similar to the "as" script above except for lwar. | |
| 22 | |
| 23 | |
| 24 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 | |
| 26 whereever you plan to put your cross-development binaries. Then, when | |
| 27 building the cross compiler, you tell it where the scripts are. | |
| 28 | |
| 29 The following worked with gcc6809 4.3.4-3: | |
| 30 | |
| 31 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/. | |
| 33 | |
| 34 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. | |
| 36 | |
| 37 3. Unpack gcc and apply the gcc6809 patch. | |
| 38 | |
| 39 4. Make sure /usr/local/coco/bin is in your PATH | |
| 40 | |
| 41 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. | |
| 43 | |
| 44 6. In a directory (other than the gcc source, say "gcc-build" at the same | |
| 45 level as the main gcc directory, do (assuming gcc 4.3.4): | |
| 46 | |
| 47 configure --enable-languages=c --target=m6809-unknown \ | |
| 48 --program-prefix=m6809-unknown- --enable-obsolete \ | |
| 49 --srcdir=../gcc-4.3.4 --disable-threads --disable-nls \ | |
| 50 --disable-libssp --prefix=/usr/local/coco \ | |
| 51 --with-as=/usr/local/coco/bin/m6809-unknown-as \ | |
| 52 --with-ld=/usr/local/coco/bin/m6809-unknown-ld \ | |
| 53 --with-ar=/usr/local/coco/bin/m6809-unknown-ar | |
| 54 | |
| 55 NOTE: the last three are required to prevent selection of the wrong binutils | |
| 56 programs at runtime. | |
| 57 | |
| 58 --with-sysroot might be useful if you have a C library involved. | |
| 59 | |
| 60 7. Run "make". If errors appear, troubleshoot. | |
| 61 | |
| 62 8. Run "make install". Note that you will have to have your PATH variable | |
| 63 for "root" set up correctly if your install prefix requires root privileges. | |
| 64 | |
| 65 The above is WOMM certified. YMMV. |