buildtools/legacy/gcc
Alexander von Gluck IV 56d94c3a71 legacy/gcc: Fix cpp cross-tool prefix
* Noticed that our gcc2 randomly produces a "cpp" instead of a i586-pc-haiku-cpp
* A quick google search turned up a vintage patch for palmos which also
  fixes this issue:
  https://github.com/jichu4n/prc-tools-remix/blob/master/prc-tools-2.3/gcc-2.95.3.palmos.diff
* Confirmed it fixes the issue, and built a x86_gcc2 image without any
  issues

Change-Id: I33959248f10b69d64a4a9e430a9c254a162bcb53
Reviewed-on: https://review.haiku-os.org/c/1583
Reviewed-by: Alex von Gluck IV <kallisti5@unixzen.com>
Reviewed-by: waddlesplash <waddlesplash@gmail.com>
2019-07-12 02:18:03 +00:00
..
config
contrib
etc Trying to fix #8063 (failure to build gcc2 when updating info files): 2013-04-19 21:58:21 +02:00
gcc legacy/gcc: Fix cpp cross-tool prefix 2019-07-12 02:18:03 +00:00
include
INSTALL
libchill
libf2c
libiberty * Created a Haiku configuration by copying the BeOS configuration and 2008-03-21 23:52:23 +00:00
libio * Created a Haiku configuration by copying the BeOS configuration and 2008-03-21 23:52:23 +00:00
libobjc
libstdc++ Fix prototype for atomic_add 2014-01-17 10:02:13 +01:00
texinfo The strcpy() usage would overwrite its own buffer. The behaviour somehow 2010-07-19 01:41:31 +00:00
.brik
.cvsignore
ChangeLog
config-ml.in
config.guess Part of #3298: 2010-08-30 16:06:12 +00:00
config.if
config.sub Part of #3298: 2010-08-30 16:06:12 +00:00
configure
configure.in * Created a Haiku configuration by copying the BeOS configuration and 2008-03-21 23:52:23 +00:00
COPYING
COPYING.LIB
FAQ
faq.html
install-sh
ltconfig Auto-generated files. Manually adjusted, since I don't trust the current 2008-03-22 00:13:53 +00:00
ltmain.sh
MAINTAINERS
Makefile.in Drop libio and libstdc++ from buildsystem of legacy gcc. 2013-07-17 19:11:17 +02:00
missing
mkinstalldirs
move-if-change
README
symlink-tree
ylwrap

		   README for GNU development tools

This directory contains various GNU compilers, assemblers, linkers, 
debuggers, etc., plus their support routines, definitions, and documentation.


Check the INSTALL directory for detailed configuration and installation
instructions.


Much of the code and documentation enclosed is copyright by
the Free Software Foundation, Inc.  See the file COPYING or
COPYING.LIB in the various directories, for a description of the
GNU General Public License terms under which you can copy the files.

REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
on where and how to report problems.