how do i actually build and link agains mylovely crossbuildenvironment?:-)

Daniel Kegel dank@kegel.com
Tue Jan 13 21:34:00 GMT 2004


John Utz wrote:
>>What's your build environment, again?  What shell do you use?
> 
> rh9 i686
> 
> [johnut01@gbcxdev johnut01]$ gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --with-system-zlib --enable-__cxa_atexit
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
> 
> [johnut01@gbcxdev johnut01]$ bash -version
> bash -version
> GNU bash, version 2.05b.0(1)-release (i386-redhat-linux-gnu)
> Copyright (C) 2002 Free Software Foundation, Inc.

My build environment exactly.  So nothing fishy there.

BTW I usually set the result to end up in /opt/crosstool,
but that shouldn't matter too much.  Just in case, here's how I build:

#!/bin/sh
set -ex
export TARBALLS_DIR=~/downloads
export RESULT_TOP=/opt/crosstool

# Really, you should do the mkdir before running this,
# and chown /opt/crosstool to yourself so you don't need to run as root.
mkdir -p /opt/crosstool

# Build the toolchain.  Takes a couple hours and a couple gigabytes.
#eval `cat i686.dat gcc-2.95.3-glibc-2.1.3.dat` sh all.sh --notest
#eval `cat i686.dat gcc-3.2.3-glibc-2.2.5.dat` sh all.sh --notest
eval `cat i686.dat gcc-3.3.2-glibc-2.2.5.dat` sh all.sh --notest

- Dan


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com



More information about the crossgcc mailing list