From 73037373b6e53d9b426fff113748860c7d6a9d4b Mon Sep 17 00:00:00 2001
From: Björn Stenberg <bjorn@haxx.se>
Date: Mon, 17 Jun 2002 13:47:20 +0000
Subject: Removed newlib

git-svn-id: svn://svn.rockbox.org/rockbox/trunk@1041 a1c6a512-1295-4272-9138-f99709370657
---
 www/cross-gcc.t | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

(limited to 'www')

diff --git a/www/cross-gcc.t b/www/cross-gcc.t
index 0915961ef8..030671a2ec 100644
--- a/www/cross-gcc.t
+++ b/www/cross-gcc.t
@@ -5,23 +5,24 @@
 In this example I will assume that you are running Linux with the bash shell.
 We will only build the C compiler along with the assembler, linker and stuff.
 Note that the procedure is exactly the same if you are running cygwin on Windows.
+
 <h2>Download the source code</h2>
 <p>
 You will need the following archives:
 <ul>
 <li>binutils-2.11.tar.gz (find it at your closest GNU FTP site)
 <li>gcc-3.0.3.tar.gz (find it at your closest GNU FTP site)
-<li>newlib-1.10.0.tar.gz (go to <a href="http://sources.redhat.com/newlib/">the newlib home page</a> for information)
 <li>(optional) gdb-5.1.1.tar.gz (find it at your closest GNU FTP site)
 </ul>
+
 <h2>Unpack the archives</h2>
 <p>
 <pre>
  /home/linus> tar zxf binutils-2.11.tar.gz
  /home/linus> tar zxf gcc-3.0.3.tar.gz
- /home/linus> tar zxf newlib-1.10.0.tar.gz
  /home/linus> tar zxf gdb-5.1.1.tar.gz
 </pre>
+
 <h2>Create the directory tree</h2>
 <p>
 <pre>
@@ -31,14 +32,7 @@ You will need the following archives:
  /home/linus/build> mkdir gcc
  /home/linus/build> mkdir gdb
 </pre>
-<h2>Create the newlib and libgloss links</h2>
-<p>
-The GCC configuration script finds the newlib and libgloss files if they are in the GCC tree. Let's create two soft links.
-<pre>
- /home/linus> cd gcc-3.0.3
- /home/linus/gcc-3.0.3> ln -s ../newlib-1.10.0/newlib .
- /home/linus/gcc-3.0.3> ln -s ../newlib-1.10.0/libgloss .
-</pre>
+
 <h2>Choose location</h2>
 <p>
 Now is the time to decide where you want the tools to be installed. This is
@@ -47,6 +41,7 @@ you do "make install".
 <p>
 In this example I have chosen "/home/linus/sh1" as my installation directory, or <i>prefix</i> as it is called. Feel free to use any prefix, like
 /usr/local/sh1 for example.
+
 <h2>Build binutils</h2>
 <p>
 We will start with building the binutils (the assembler, linker and stuff).
@@ -58,6 +53,7 @@ in the /home/linus/sh1 directory.
  /home/linus/build/binutils> make
  /home/linus/build/binutils> make install
 </pre>
+
 <h2>Build GCC</h2>
 <p>
 Now you are ready to build GCC. To do this, you must have the newly built
@@ -65,10 +61,11 @@ binutils in the PATH.
 <pre>
  /home/linus> export PATH=/home/linus/sh1/bin:$PATH
  /home/linus> cd build/gcc
- /home/linus/gcc> ../../gcc-3.0.3/configure --target=sh-elf --prefix=/home/linus/sh1 --with-newlib --enable-languages=c
+ /home/linus/gcc> ../../gcc-3.0.3/configure --target=sh-elf --prefix=/home/linus/sh1 --enable-languages=c
  /home/linus/build/gcc> make
  /home/linus/build/gcc> make install
 </pre>
+
 <h2>Build GDB</h2>
 <p>
 If you are planning to debug your code with GDB, you have to build it as well.
@@ -79,6 +76,7 @@ If you are planning to debug your code with GDB, you have to build it as well.
  /home/linus/build/gdb> make
  /home/linus/build/gdb> make install
 </pre>
+
 <h2>Done</h2>
 <p>
 If someone up there likes you, you now have a working tool chain for SH1.
-- 
cgit v1.2.3