README - elf2flt----------------Copyright (C) 2001-2002, SnapGear (www.snapgear.com)davidm@snapgear.comgerg@snapgear.comElf2flt with PIC, ZFLAT and full reloc support. Currently supportedtargets include: m68k/ColdFire, ARM, Sparc, NEC v850.COMPILING:You need an appropriate libbfd.a and libiberty.a for your target to build this tool. They are normally part of the binutils package.To compile elf2flt do:    ./configure --target=<ARCH> --with-libbfd=<libbfd.a> --with-libiberty=<libiberty.a>    make    make installThe <ARCH> argument to configure specifies what the target architecture is.This should be the same target as you used to build the binutils and gcccross development tools. The --with-libbfd and --with-libiberty argumentsspecify where the libbfd.a and libiberty.a library files are to use.FILES:README      - this fileconfigure   - autoconf configuration shell scriptconfigure.in- original autoconf fileconfig.*    - autoconf support scriptsMakefile.in - Makefile template used by configureelf2flt.c   - the sourceflthdr.c    - flat header manipulation programflat.h      - header from uClinux kernel sourceself2flt.ld  - an example linker script that works for C/C++ and uClinuxld-elf2flt  - A linker replacement that implements a -elf2flt option for the              linker and runs elf2flt automatically for you.  It auto              detects PIC/non-PIC code and adjusts it's option accordingly.              It uses the environment variable FLTFLAGS when running              elf2flt.  It runs /.../m68k-elf-ld.real to do the actual              linking.TIPS:The ld-elf2flt produces 2 files as output.  The binary flat file X, andX.gdb which is used for debugging and PIC purposes.The '-p' option requires an elf executable linked at address 0.  Theelf2flt.ld provided will generate the correct format binary when linkedwith the real linker with *no* '-r' option for the linker.The '-r' flag can be added to PIC builds to get contiguous code/data.  Thisis good for loading application symbols into gdb (add-symbol-file XXX.gdb).