Crosstool-NG - Revision history

Jcmvbkbc: update ct-ng status

2015-11-19T03:04:00Z

update ct-ng status

← Older revision		Revision as of 03:04, 19 November 2015
Line 5:		Line 5:
	== Configure and build Crosstool-NG ==		== Configure and build Crosstool-NG ==

	~~The~~ mainline ~~repository for~~ crosstool-NG ~~does not yet include~~ support for Xtensa, so you need ~~to clone~~ the ~~repository from linux-xtensa~~.~~org:~~		Starting with release 1.22.0 the mainline crosstool-NG repository includes support for Xtensa. Using tip of the cloned git tree for work is not always a good idea, unless you need the latest mainline changes using official releases (marked by tags) would give more predictable results.

	git clone https://github.com/~~foss~~-~~xtensa~~/crosstool-NG.git		git clone https://github.com/crosstool-ng/crosstool-ng.git
			git checkout crosstool-ng-1.22.0

	=== Build ct-ng ===		=== Build ct-ng ===

	ct-ng is similar to the command 'make' for other projects, and is used to configure and build the toolchain. Since we cloned it from the repository, it is not yet ~~preconfigured with 'autoconf'~~, ~~so run autoconf first~~:		ct-ng is similar to the command 'make' for other projects, and is used to configure and build the toolchain. Since we cloned it from the repository, its build system is not configured yet, use ./bootstrap script to create it:

	~~autoconf~~		./bootstrap

	The next step is to configure ct-ng for your system. The default installation path is /usr/local/ but can be overwritten with the --prefix option. ~~In this example, we install it in the current directory. Note that the prefix~~ option ~~requires an absolute path, so we use $PWD in this example~~:		The next step is to configure ct-ng for your system. The default installation path is /usr/local/ but can be overwritten with the --prefix option. It is also possible to configure ct-ng for use without installation with --enable-local configure option:

	./configure --~~prefix=$PWD/usr~~		./configure --enable-local

	Finally, run 'make ~~install~~' to build ct-ng and install it:		Finally, run 'make' to build ct-ng (and 'make install' to install it if needed):

	make ~~install~~		make

			=== Xtensa core overlay file ===
			The overlay file includes patches for toolchain tools, such as compiler, assembler, and debugger, that are required to support a specific Xtensa processor configuration. Tensilica provides such an overlay as part of the processor download, however, it needs to be reformatted to match the specific format required by the crosstool-NG. For a script to convert the overlay file, and additional information, please go to [[Toolchain Overlay File]]. The current version of crosstool-NG requires that the overlay file name has the format xtensa_<CORE_NAME>.tar, where CORE_NAME can be any user selected name.

	== Building a 'bare' toolchain without a C-library ==		== Building a 'bare' toolchain without a C-library ==
Line 31:		Line 35:
	./ct-ng menuconfig		./ct-ng menuconfig

	Make the following changes (---> means to enter the sub-menu). We are assuming that the overlay tar image (~~OVERLAY_TARFILE~~) has been copied to ABSOLUTE_PATH_TO_OVERLAY~~. More information about the overlay file can be found [[Create Overlay\|here]]. Note that the processor configuration name is currently not used~~.		Make the following changes (---> means to enter the sub-menu). We are assuming that the overlay tar image (xtensa_<CORE_NAME>.tar) has been copied to ABSOLUTE_PATH_TO_OVERLAY.

	Target options --->		Target options --->
	Target Architecture (xtensa)		Target Architecture (xtensa)
	Target Architecture Variant (Custom Xtensa processor configuration)		Target Architecture Variant (Custom Xtensa processor configuration)
	(~~PROCESSOR_NAME~~) Custom Xtensa process configuration ~~name~~		(CORE_NAME) Custom Xtensa process configuration file name
	~~(OVERLAY_TARFILE) Custom Xtensa overlay~~ file name
	(ABSOLUTE_PATH_TO_OVERLAY) Full path to custom Xtensa processor configurations		(ABSOLUTE_PATH_TO_OVERLAY) Full path to custom Xtensa processor configurations

	C-library --->		C-library --->
	C library (none)		C library (none)
Line 59:		Line 62:
	xtensa-unknown-linux-gnu-gcc t.c		xtensa-unknown-linux-gnu-gcc t.c

			== Building uClibc-ng based toolchain ==

			=== Configure the toolchain ===

			Similar to the 'bare' version above, the first step is to configure crosstool-NG. Simply run

			./ct-ng menuconfig

			and make the following changes (---> means to enter the sub-menu).

			Paths and misc options --->
			[*] Try features marked as EXPERIMENTAL

			Target options --->
			Target Architecture (xtensa)
			Target Architecture Variant (Custom Xtensa processor configuration)
			(CORE_NAME) Custom Xtensa process configuration name
			(ABSOLUTE_PATH_TO_OVERLAY) Full path to custom Xtensa processor configurations

			Operating system --->
			Target OS (linux)

			C-library --->
			C library (uClibc)

			=== Build and install the toolchain ===

			Finally, build and install the toolchain.

			./ct-ng build

	== Building a 'glibc' based toolchain ''(experimental)'' ==		== Building a 'glibc' based toolchain ''(experimental)'' ==
Line 74:		Line 107:
	./ct-ng menuconfig		./ct-ng menuconfig

	and make the following changes (---> means to enter the sub-menu)~~. We are assuming that the overlay file ([[Create Overlay]]) has been copied to ABSOLUTE_PATH_TO_OVERLAY/CPUNAME.tar.gz~~.		and make the following changes (---> means to enter the sub-menu).

	Paths and misc options --->		Paths and misc options --->
Line 82:		Line 115:
	Target Architecture (xtensa)		Target Architecture (xtensa)
	Target Architecture Variant (Custom Xtensa processor configuration)		Target Architecture Variant (Custom Xtensa processor configuration)
	(~~PROCESSOR_NAME~~) Custom Xtensa process configuration ~~name~~		(CORE_NAME) Custom Xtensa process configuration name
	~~(OVERLAY_TARFILE) Custom Xtensa overlay file~~ name
	(ABSOLUTE_PATH_TO_OVERLAY) Full path to custom Xtensa processor configurations		(ABSOLUTE_PATH_TO_OVERLAY) Full path to custom Xtensa processor configurations

	C-library --->		C-library --->
	C library (glibc)		C library (glibc)

Chris at 19:36, 11 November 2013

2013-11-11T19:36:06Z

← Older revision		Revision as of 19:36, 11 November 2013
Line 7:		Line 7:
	The mainline repository for crosstool-NG does not yet include support for Xtensa, so you need to clone the repository from linux-xtensa.org:		The mainline repository for crosstool-NG does not yet include support for Xtensa, so you need to clone the repository from linux-xtensa.org:

	git clone ~~git@~~github.com:foss-xtensa/crosstool-NG.git		git clone https://github.com/foss-xtensa/crosstool-NG.git

	=== Build ct-ng ===		=== Build ct-ng ===

Chris: /* Building a 'glibc' based toolchain (experimental) */

2013-11-11T06:33:42Z

Building a 'glibc' based toolchain (experimental)

← Older revision		Revision as of 06:33, 11 November 2013
Line 61:		Line 61:

	== Building a 'glibc' based toolchain ''(experimental)'' ==		== Building a 'glibc' based toolchain ''(experimental)'' ==

			NOTE THAT THE REPOSITORY IS CURRENTLY NOT AVAILABLE.

	The glibc port is experimental at the moment and also not part of the main repository yet. A version for Xtensa can be found on linux-xtensa.org, so you can clone it from there:		The glibc port is experimental at the moment and also not part of the main repository yet. A version for Xtensa can be found on linux-xtensa.org, so you can clone it from there:

	git clone git://~~linux-xtensa~~.~~org~~/git/glibc		git clone git://.../git/glibc

	=== Configure the toolchain ===		=== Configure the toolchain ===

Chris: /* Configure and build Crosstool-NG */

2013-11-11T06:24:26Z

Configure and build Crosstool-NG

← Older revision		Revision as of 06:24, 11 November 2013
Line 7:		Line 7:
	The mainline repository for crosstool-NG does not yet include support for Xtensa, so you need to clone the repository from linux-xtensa.org:		The mainline repository for crosstool-NG does not yet include support for Xtensa, so you need to clone the repository from linux-xtensa.org:

	git clone git:~~//linux~~-xtensa~~.org/git~~/crosstool-NG		git clone git@github.com:foss-xtensa/crosstool-NG.git

	=== Build ct-ng ===		=== Build ct-ng ===

Chris at 21:21, 10 March 2013

2013-03-10T21:21:40Z

← Older revision		Revision as of 21:21, 10 March 2013
Line 1:		Line 1:
	== Overview ==		== Overview ==

	~~crosstool~~-NG provides a system to build a complete toolchain. It supports ~~the c~~-libraries uClibc, glibc, and eglibc, but can also be used to build a ~~'bare'~~ toolchain. The following ~~describes~~ the steps to build a toolchain tailored for an Xtensa configuration~~. In this example, we are building a 'bare' toolchain for the DC_D_233L processor configuration. 'Bare' in this sense means a toolchain without a c-library~~.		Crosstool-NG provides a system to build a complete toolchain. It supports various C-libraries (newlib, uClibc, glibc, and eglibc), but can also be used to build a toolchain without a C-library. The following paragraphs describe the steps to build a toolchain tailored for an Xtensa configuration.

	== ~~Building a 'bare' toolchain~~ ==		== Configure and build Crosstool-NG ==

	The mainline repository for crosstool-NG does not yet include support for Xtensa, so you need to clone the repository from linux-xtensa.org:		The mainline repository for crosstool-NG does not yet include support for Xtensa, so you need to clone the repository from linux-xtensa.org:
Line 11:		Line 11:
	=== Build ct-ng ===		=== Build ct-ng ===

	ct-ng is similar to the command 'make' for other projects, and is used to configure and build the toolchain. ~~Because this is not a released package but~~ cloned from a repository, it is not yet preconfigured with 'autoconf'~~. So~~, ~~the first step is to~~ run autoconf:		ct-ng is similar to the command 'make' for other projects, and is used to configure and build the toolchain. Since we cloned it from the repository, it is not yet preconfigured with 'autoconf', so run autoconf first:

	autoconf		autoconf

	The next step is to configure ct-ng for your system~~. crosstool-NG needs to install additional components~~. The default path is /usr/local/ but can be overwritten with the --prefix option. In this example, we install ~~all additional files under $PWD~~ in the current directory. Note that the prefix option requires an absolute path, so we use $PWD ~~here~~:		The next step is to configure ct-ng for your system. The default installation path is /usr/local/ but can be overwritten with the --prefix option. In this example, we install it in the current directory. Note that the prefix option requires an absolute path, so we use $PWD in this example:

	./configure --prefix=$PWD/usr		./configure --prefix=$PWD/usr

	Finally, run 'make install' to build ct-ng and install ~~the additional files~~:		Finally, run 'make install' to build ct-ng and install it:

	make install		make install

	==~~= Build the~~ toolchain ===		== Building a 'bare' toolchain without a C-library ==

	The first step is to configure ~~crosstool-NG. Simply run~~		=== Configure the toolchain ===

			The first step is to configure the toolchain:

	./ct-ng menuconfig		./ct-ng menuconfig

	Make ~~sure to make~~ the following changes (---> means to enter the sub-menu). We are assuming that the overlay ~~file~~ (~~src/xtensa-config-overlay.tar.gz~~) has been copied to ~~/HOME/~~Overlay~~/CPUNAME~~.~~tar~~.~~gz.~~		Make the following changes (---> means to enter the sub-menu). We are assuming that the overlay tar image (OVERLAY_TARFILE) has been copied to ABSOLUTE_PATH_TO_OVERLAY. More information about the overlay file can be found [[Create Overlay\|here]]. Note that the processor configuration name is currently not used.

	~~Paths and misc options --->~~
	~~[*] Try features marked as EXPERIMENTAL~~

	Target options --->		Target options --->
	Target Architecture (xtensa)		Target Architecture (xtensa)
	Target Architecture Variant (Custom Xtensa processor configuration)		Target Architecture Variant (Custom Xtensa processor configuration)
	(~~CPUNAME~~) Custom Xtensa process configuration name		(PROCESSOR_NAME) Custom Xtensa process configuration name
	(~~/HOME/Overlay/~~) Full path to custom Xtensa processor configurations		(OVERLAY_TARFILE) Custom Xtensa overlay file name
			(ABSOLUTE_PATH_TO_OVERLAY) Full path to custom Xtensa processor configurations

	C-library --->		C-library --->
	C library (none)		C library (none)

			The default directory for the created toolchain is $HOME/x-tools, but can be configured under 'Paths and misc options':

			Paths and misc options --->
			(${HOME}/x-tools/${CT_TARGET}) Prefix directory

	=== Build and install the toolchain ===		=== Build and install the toolchain ===

	Finally, build and install the toolchain.		Finally, build and install the toolchain.
	~~The default install directory is $HOME/x-tools, unless changed during the~~
	~~configuration step above.~~

	./ct-ng build		./ct-ng build
Line 55:		Line 58:
	export PATH=$PATH:$HOME/x-tools/xtensa-unknown-linux-gnu/bin		export PATH=$PATH:$HOME/x-tools/xtensa-unknown-linux-gnu/bin
	xtensa-unknown-linux-gnu-gcc t.c		xtensa-unknown-linux-gnu-gcc t.c


	== Building a 'glibc' based toolchain ''(experimental)'' ==		== Building a 'glibc' based toolchain ''(experimental)'' ==

	The glibc port is experimental at the moment and also not part of the main repository yet. A version for Xtensa is on linux-xtensa.org, so you ~~need to~~ clone ~~the glibc and crosstool-NG repositories~~:		The glibc port is experimental at the moment and also not part of the main repository yet. A version for Xtensa can be found on linux-xtensa.org, so you can clone it from there:

	~~git clone git://linux-xtensa.org/git/crosstool-NG~~
	git clone git://linux-xtensa.org/git/glibc		git clone git://linux-xtensa.org/git/glibc

	[~~more instructions~~ to ~~follow~~...]		=== Configure the toolchain ===

			Similar to the 'bare' version above, the first step is to configure crosstool-NG. Simply run

			./ct-ng menuconfig

			and make the following changes (---> means to enter the sub-menu). We are assuming that the overlay file ([[Create Overlay]]) has been copied to ABSOLUTE_PATH_TO_OVERLAY/CPUNAME.tar.gz.

			Paths and misc options --->
			[*] Try features marked as EXPERIMENTAL

			Target options --->
			Target Architecture (xtensa)
			Target Architecture Variant (Custom Xtensa processor configuration)
			(PROCESSOR_NAME) Custom Xtensa process configuration name
			(OVERLAY_TARFILE) Custom Xtensa overlay file name
			(ABSOLUTE_PATH_TO_OVERLAY) Full path to custom Xtensa processor configurations

			C-library --->
			C library (glibc)
			glibc version (Custom glibc)
			(ABSOLUTE_PATH_TO_glibc-2.17) Full path to custom glibc source
			(ports) Extra addons

			=== Build and install the toolchain ===

			Finally, build and install the toolchain.

			./ct-ng build

Chris at 23:54, 9 March 2013

2013-03-09T23:54:44Z

← Older revision		Revision as of 23:54, 9 March 2013
Line 55:		Line 55:
	export PATH=$PATH:$HOME/x-tools/xtensa-unknown-linux-gnu/bin		export PATH=$PATH:$HOME/x-tools/xtensa-unknown-linux-gnu/bin
	xtensa-unknown-linux-gnu-gcc t.c		xtensa-unknown-linux-gnu-gcc t.c

			== Building a 'glibc' based toolchain ''(experimental)'' ==

			The glibc port is experimental at the moment and also not part of the main repository yet. A version for Xtensa is on linux-xtensa.org, so you need to clone the glibc and crosstool-NG repositories:

			git clone git://linux-xtensa.org/git/crosstool-NG
			git clone git://linux-xtensa.org/git/glibc

			[more instructions to follow...]

Chris at 22:21, 2 March 2013

2013-03-02T22:21:26Z

← Older revision		Revision as of 22:21, 2 March 2013
Line 29:		Line 29:
	./ct-ng menuconfig		./ct-ng menuconfig

	Make sure to make the following changes (---> means to enter the sub-menu)		Make sure to make the following changes (---> means to enter the sub-menu). We are assuming that the overlay file (src/xtensa-config-overlay.tar.gz) has been copied to /HOME/Overlay/CPUNAME.tar.gz.

	Paths and misc options --->		Paths and misc options --->
Line 36:		Line 36:
	Target options --->		Target options --->
	Target Architecture (xtensa)		Target Architecture (xtensa)
	Target Architecture Variant (Custom Xtensa processor ~~configur...~~		Target Architecture Variant (Custom Xtensa processor configuration)
	(~~DC_D_233L~~) Custom Xtensa process configuration name		(CPUNAME) Custom Xtensa process configuration name
			(/HOME/Overlay/) Full path to custom Xtensa processor configurations

	C-library --->		C-library --->

Chris: New page: == Overview == crosstool-NG provides a system to build a complete toolchain. It supports the c-libraries uClibc, glibc, and eglibc, but can also be used to build a 'bare' toolchain. The f...

2013-03-02T22:15:49Z

New page: == Overview == crosstool-NG provides a system to build a complete toolchain. It supports the c-libraries uClibc, glibc, and eglibc, but can also be used to build a 'bare' toolchain. The f...

New page

== Overview ==

crosstool-NG provides a system to build a complete toolchain. It supports the c-libraries uClibc, glibc, and eglibc, but can also be used to build a 'bare' toolchain. The following describes the steps to build a toolchain tailored for an Xtensa configuration. In this example, we are building a 'bare' toolchain for the DC_D_233L processor configuration. 'Bare' in this sense means a toolchain without a c-library.

== Building a 'bare' toolchain ==

The mainline repository for crosstool-NG does not yet include support for Xtensa, so you need to clone the repository from linux-xtensa.org:

git clone git://linux-xtensa.org/git/crosstool-NG

=== Build ct-ng ===

ct-ng is similar to the command 'make' for other projects, and is used to configure and build the toolchain. Because this is not a released package but cloned from a repository, it is not yet preconfigured with 'autoconf'. So, the first step is to run autoconf:

autoconf

The next step is to configure ct-ng for your system. crosstool-NG needs to install additional components. The default path is /usr/local/ but can be overwritten with the --prefix option. In this example, we install all additional files under $PWD in the current directory. Note that the prefix option requires an absolute path, so we use $PWD here:

./configure --prefix=$PWD/usr

Finally, run 'make install' to build ct-ng and install the additional files:

make install

=== Build the toolchain ===

The first step is to configure crosstool-NG. Simply run

./ct-ng menuconfig

Make sure to make the following changes (---> means to enter the sub-menu)

Paths and misc options --->
[*] Try features marked as EXPERIMENTAL

Target options --->
Target Architecture (xtensa)
Target Architecture Variant (Custom Xtensa processor configur...
(DC_D_233L) Custom Xtensa process configuration name

C-library --->
C library (none)

=== Build and install the toolchain ===

Finally, build and install the toolchain.
The default install directory is $HOME/x-tools, unless changed during the
configuration step above.

./ct-ng build

=== Test it ===

export PATH=$PATH:$HOME/x-tools/xtensa-unknown-linux-gnu/bin
xtensa-unknown-linux-gnu-gcc t.c