crosstool-ng/docs
Yann E. MORIN" 3c351b899d docs: update credtis, point to the repository log
The docs/CREDITS file dates back to the SVN repository.
Now that we use Mercurial, the repository stores appropriate
authorship for each commit. Say so in the CREDITS.
2010-05-30 18:19:05 +02:00
..
CREDITS docs: update credtis, point to the repository log 2010-05-30 18:19:05 +02:00
ct-ng.1.in Update documentation. 2008-06-25 14:06:49 +00:00
known-issues.txt docs: update the known issues 2010-04-30 14:33:07 +02:00
overview.txt docs/overview.txt: Provide short mercurial HOWTO 2010-05-22 18:48:50 +02:00
README.macos.txt docs: Provide new Readme for MacOS 2010-05-25 18:25:11 +02:00

22 May 2010 - Titus

Prerequisites and instructions for using crosstool-NG for building a cross
toolchain on MacOS as host.

0) Mac OS Snow Leopard, with Developer Tools 3.2 installed, or
   Mac OS Leopard, with Developer Tools & newer gcc (>= 4.3) installed
   via macports

1) You have to use a case sensitive file system for ct-ng's build and target
   directories. Use a disk or disk image with a case sensitive fs that you
   mount somewhere.

2) Install macports (or similar easy means of installing 3rd party software),
   make sure that macport's bin dir is in your PATH.
   Furtheron assuming it is /opt/local/bin.

3) Install (at least) the following macports
   ncurses
   lzmautils
   libtool
   binutils
   gsed
   gawk
   gcc43 (only necessary for Leopard OSX 10.5)

   On Leopard, make sure that the macport's gcc is called with the default
   commands (gcc, g++,...), e.g. via macport gcc_select

4) run ct-ng's configure with the following tool configuration
   (assuming you have installed the tools via macports in /opt/local):
   ./configure --with-sed=/opt/local/bin/gsed           \
               --with-libtool=/opt/local/bin/glibtool   \
               --with-objcopy=/opt/local/bin/gobjcopy   \
               --with-objdump=/opt/local/bin/gobjdump   \
               --with-readelf=/opt/local/bin/greadelf   \
               [...other configure parameters as you like...]

5) proceed as described in standard documentation