Johannes Pfau 586e30f726 Only create ${CT_TARGET}-cc${ext} symlink if ${CT_TARGET}-gcc exists
Without this canadion cross builds create invalid symlinks:
When the code in do_cc_core_backend is called there is no
${CT_TARGET}-gcc in the install directory. Therefore ext is empty and
we create a link to ${CT_TARGET}-gcc. The final compiler
step then installs ${CT_TARGET}-gcc.exe and creates a working
${CT_TARGET}-cc.exe symlink but we still keep the invalid link
as well.

Signed-off-by: Johannes Pfau <johannespfau@gmail.com>
2015-04-07 20:14:26 +02:00
2015-03-07 15:05:35 +01:00
2012-03-06 21:36:10 +01:00
2014-12-10 16:51:44 +00:00
2014-12-10 16:51:44 +00:00
2014-09-08 23:58:37 +02:00
2013-09-14 02:45:23 +01:00
2013-01-10 21:01:59 +01:00
2014-05-07 18:40:48 +02:00

This is the README for crosstool-NG

Crosstool-NG follows the autoconf dance. So, to get you
kick-started, just run:
    ./configure --help

If you are using a development snapshot, you'll have to
create the configure script, first. Just run:
    ./bootstrap

You will find the documentation in the directory 'docs'.
Here is a quick overview of what you'll find there:
  0 - Table of content
  1 - Introduction
  2 - Installing crosstool-NG
  3 - Configuring a toolchain
  4 - Building the toolchain
  5 - Using the toolchain
  6 - Toolchain types
  7 - Contributing
  8 - Internals
  A - Credits
  B - Known issues
  C - Misc. tutorials

You can also point your browser at:
  http://crosstool-ng.org/

Aloha!
Description
A versatile (cross-)toolchain generator.
Readme 20 MiB
Languages
Shell 50.9%
C 27.4%
M4 16.9%
Makefile 1.9%
Yacc 1.4%
Other 1.5%