Mercurial > hg-old > index.cgi
comparison extra/README @ 208:06effa2faea1
Added some info on building gcc6809 to use lwtools
author | lost |
---|---|
date | Tue, 21 Apr 2009 02:57:37 +0000 |
parents | 3711cd1c01e2 |
children | b34071013404 |
comparison
equal
deleted
inserted
replaced
207:0926c29426f4 | 208:06effa2faea1 |
---|---|
18 | 18 |
19 ar | 19 ar |
20 | 20 |
21 Similar to the "as" script above except for lwar. | 21 Similar to the "as" script above except for lwar. |
22 | 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 You should probably name them m6809-unknown-none-{ar,as,ld} or similar | |
30 depending on your gcc build target. Then you'll want to get the gcc6809 | |
31 patch and patch the correct gcc source code. Then use a configure line | |
32 similar to the following: | |
33 | |
34 configure --enable-languages=c --target=m6809-coco | |
35 --program-prefix=m6809-coco-lwos- --enable-obsolete | |
36 --srcdir=/home/lost/gcc6809/src/gcc-4.3.3 --disable-threads --disable-nls | |
37 --disable-libssp --prefix=/usr/local/coco --with-as=/usr/local/coco/bin/as | |
38 --with-ld=/usr/local/coco/bin/ld --with-sysroot=/usr/local/coco | |
39 | |
40 Obviously adjust various paths to match what you're doing. | |
41 | |
42 The exact mechanics of configuring and getting gcc to install correctly is | |
43 left as an exercise to the dedicated masochist. |