comparison extra/README @ 410:acaafc70044b

Fixed "=" pseudo op to work correctly
author lost@l-w.ca
date Sun, 08 Aug 2010 23:47:16 -0600
parents 1c31e9005ff7
children
comparison
equal deleted inserted replaced
409:cba03436c720 410:acaafc70044b
26 whereever you plan to put your cross-development binaries. Then, when 26 whereever you plan to put your cross-development binaries. Then, when
27 building the cross compiler, you tell it where the scripts are. 27 building the cross compiler, you tell it where the scripts are.
28 28
29 You should probably name them m6809-unknown-none-{ar,as,ld} or similar 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 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 31 patch and patch the correct gcc source code. You probably want to add
32 similar to the following: 32 m6809-unknown-none-ranlib as a symblink to /bin/true, too.
33 33
34 configure --enable-languages=c --target=m6809-coco 34 Then, you can skip the bits in the install instructions that install
35 --program-prefix=m6809-coco-lwos- --enable-obsolete 35 "binutils" and so on. A simple "make" in the "build-6809" directory should
36 --srcdir=/home/lost/gcc6809/src/gcc-4.3.3 --disable-threads --disable-nls 36 do. At least it does with gcc6809-4.3.4-3.
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 37
42 The exact mechanics of configuring and getting gcc to install correctly is 38 The exact mechanics of configuring and getting gcc to install correctly is
43 left as an exercise to the dedicated masochist. 39 left as an exercise to the dedicated masochist.