Source code is normally in /usr/cygnus/release_name/src. Good practice is to configure and build the source in another directory—any other clean directory will do. The build process may take hundreds of megabytes of disk space. Never build your toolkit in the source directory.
The default action for configure is to configure a native toolchain for the host on which you run the script. At minimum, you should specify –-prefix and –-exec-prefix to point to your installation directory. Although –exec-prefix is not required for single-host installations, we still recommend using it for all configurations. For cross-compiler toolchains, you must also specify --target. The following examples use a directory for the build location named /usr/cygnus/release_name/build.
To configure a toolchain in /opt/cygnus targeting an Hitachi SH embedded board, use the following example’s steps.
1.
mkdir /usr/cygnus/release_name/build
2.
cd
/usr/cygnus/release_name/build
3.
/usr/cygnus/release_name/src/configure
--prefix=/opt/cygnus/release_name
\
--exec-prefix=/opt/cygnus/release_name/H-sparc-sun-sunos4.1
\
&
753
nbsp;--target=sh-hms
To configure a native toolchain
for HP/UX 9, use the following example’s steps.
1.
mkdir /usr/cygnus/release_name/build
2.
cd
/usr/cygnus/release_name/build
/usr/cygnus/release_name/src/configure
--prefix=/opt/cygnus/release_name
\
--exec-prefix=/opt/cygnus/release_name/H-hppa1.1-hp-hpux