From: Enrico Colombini <erix@mclink.it>
To: crossgcc@sources.redhat.com
Subject: CrossGCC build script (including fixes)
Date: Tue, 10 Oct 2000 00:52:00 -0000 [thread overview]
Message-ID: <3.0.6.32.20001010094747.007d2100@mail.mclink.it> (raw)
After gathering information from the CrossGCC FAQ and from this list, I
successfuly built a 68k cross-compiler (the compiler works, but I haven't
tried out the library yet).
Here is the script I used; it is not very elegant and it uses up a lot of
space, but it seems to work fine, both on Linux redHat 6.0 and on CygWin
(CygWin tends to slow down to a trickle on Windows 98, but that is another
problem).
It would be a good idea to delete the "build" subdirectories at the end of
the process (or to modify the script to use a single "build" directory if
space is tight).
Enrico
--------------
#!/bin/sh
# Build a CrossGCC for newlib for embedded sistems
# Enrico Colombini <erix@mclink.it> October 2000
# It works on my RedHat 6.0 Linux box. I make no other claims.
#
# Thanks to Scott Howard for the CrossGCC FAQ, to Jo~ao Cadamuro
# and to many people on the CrossGCC list for the fixes, and to
# Marco Morocutti for cooperation and support
# = 1 = Before executing this, get the sources for:
# binutils, gcc, newlib, gdb
# and unpack them in the <src> directory (say /home/erix/crossrc)
# (e.g. tar zxvf binutils-2_10_tar.gz)
# thus creating four corresponding subdirectories
# = 2 = Adjust the lines below to configure for your system:
#
prefix=/home/erix/crossgcc # Destination directory
target=m68k-coff # Target system
binutilsdir=binutils-2.10 # Directories created by unpacking sources
gccdir=gcc-2.95.2
newlibdir=newlib-1.8.2
gdbdir=gdb-5.0
# - 3 - Execute this shell script from <src>: ./buildcross
# Create destination directory
mkdir -p $prefix
# Compile binutils
mkdir -p build$binutilsdir
cd build$binutilsdir
../$binutilsdir/configure --target=$target --prefix=$prefix -v
make all install
cd ..
# Add executables to path, they'll be needed later
PATH=$prefix/bin:$PATH
echo $PATH
# Add symbolic links to newlib into gcc source
cd $gccdir
ln -s ../$newlibdir/newlib newlib
ln -s ../$newlibdir/libgloss libgloss
cd ..
# Compile gcc
mkdir -p build$gccdir
cd build$gccdir
../$gccdir/configure --target=$target --prefix=$prefix --with-newlib
--enable-languages= -v
make all install
cd ..
# Compile newlib
mkdir -p build$newlibdir
cd build$newlibdir
../$newlibdir/configure --target=$target --prefix=$prefix -v
make all install
cd ..
# Compile gdb
mkdir -p build$gdbdir
cd build$gdbdir
../$gdbdir/configure --target=$target --prefix=$prefix -v
make all install
cd ..
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-10-10 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-10 0:52 Enrico Colombini [this message]
2000-10-10 5:28 ` João Cadamuro Junior
2000-10-11 1:03 ` Enrico Colombini
2000-10-11 6:27 ` João Cadamuro Junior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3.0.6.32.20001010094747.007d2100@mail.mclink.it \
--to=erix@mclink.it \
--cc=crossgcc@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).