User:Roirodriguez - Revision history

Openuas: /* Toolchain compilation */

2010-08-06T16:40:43Z

Toolchain compilation

← Older revision		Revision as of 10:40, 6 August 2010
Line 243:		Line 243:
	QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?		QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?

	~~A: Change your CC environmental variable~~ to the ~~version you want, as~~ in ~~CC=~~gcc-~~3.4.~~		Changinge the symbolic link is not really the way to do it as we all expected... we are not the olny ones with this wish. therefore support for this is build in right in gcc (gcc -V, mind the UPPERcase V)You can have as many compilers, as you want. See below for useing it win configue and make, Examples, using compilers :
	~~Before compiling a program~~, in the ~~same terminal in which~~ you ~~are going to run configure~~ and make, ~~type~~:

	~~$ export CC=gcc-3.4~~

	~~A: Better use mybe "~~gcc -V" the ~~build~~ in ~~function of gcc to switch versions~~		./configure CC=gcc-3.4 CXX=g++-3.4
			./configure CC=gcc-4.1 CXX=g++-4.1

			and / or

			make CC=gcc-3.4 CXX=g++-3.4
			make CC=gcc-4.1 CXX=g++-4.1

			gcc-3.4 -o <object> file.c
			.....
			gcc -v , gcc-4.1 -v , gcc-3.4 -v .

			Ofcourse make first sure you do have the compiles in the first place

			====== Crosscompiler compilation ======

	Now we download gcc, binuitils and newlib, which can be found at:		Now we download gcc, binuitils and newlib, which can be found at:
Line 263:		Line 274:
	If you download the versions above, and follow the instructions at that link being sure you follow my observations you are done.		If you download the versions above, and follow the instructions at that link being sure you follow my observations you are done.

	Now, remember to undo that symlink:		Now, remember to undo that symlink if you used that method insted of the make CC=gcc-3.4 CXX=g++-3.4 option:

	sudo unlink /usr/bin/gcc		$ sudo unlink /usr/bin/gcc
	sudo ln -s /usr/bin/gcc-4.4 /usr/bin/gcc # Change 4.4 by your most recent gcc compiler, see ls -l /usr/bin/gcc-*		$ sudo ln -s /usr/bin/gcc-4.4 /usr/bin/gcc # Change 4.4 by your most recent gcc compiler, see ls -l /usr/bin/gcc-*

	~~QUESTION~~: Better build instructions? More accurate t-arm-ef file? Can anybody test the compiler (i'll do as soon as i can).		QUESTIONS:
			# Better build instructions?
			## A: Yes, working on it see page [Install_paparazzi_and_everything_from_scratch from scratch], as soon as it works will update the ARM script on that page. Rest already work just fine.(OpenUAS)
			# More accurate t-arm-elf file?
			## A:
			# Can anybody test the compiler (I'll do as soon as I can).
			## A: Will do as soon as the installation process worked out (OpenUAS)

	===== Debian packages =====		===== Debian packages =====

Openuas at 16:07, 6 August 2010

2010-08-06T16:07:01Z

← Older revision		Revision as of 10:07, 6 August 2010
Line 224:		Line 224:
	* [http://es.archive.ubuntu.com/ubuntu/pool/universe/g/gcc-3.4/gcc-3.4_3.4.6-8ubuntu2_amd64.deb gcc-3.4]		* [http://es.archive.ubuntu.com/ubuntu/pool/universe/g/gcc-3.4/gcc-3.4_3.4.6-8ubuntu2_amd64.deb gcc-3.4]

	~~Now we need to be sure our 3.4~~ compiler ~~will be~~ used ~~to compile the cross-compiler instead the version 4 system default:~~		First see the current gcc compiler used, type

	sudo rm /usr/bin/gcc		$ ls -alh /urs/bin/gcc
	sudo ln -s /usr/bin/gcc-3.4 /usr/bin/gcc
			This give someting that looks like

			lrwxrwxrwx 1 root root 7 2010-08-06 15:45 /usr/bin/gcc -> gcc-4.4

			Memorize it, or write this down, we need later to restore our original settings.

			Now we need to be sure our 3.4 compiler will be used to compile the cross-compiler instead the version 4.x system default:

			$ sudo unlink /usr/bin/gcc
			$ sudo ln -s /usr/bin/gcc-3.4 /usr/bin/gcc

	We will undo this once finished.		We will undo this once finished.
Line 233:		Line 243:
	QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?		QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?

	A: Change your CC environmental variable to the version you want, as in ~~$ export~~ CC=gcc-3.4		A: Change your CC environmental variable to the version you want, as in CC=gcc-3.4.
	Before compiling a program, in the same terminal in which you are going to run configure/make, type:		Before compiling a program, in the same terminal in which you are going to run configure and make, type:
	~~Code:~~
			$ export CC=gcc-3.4
	$ export CC=~~gcc32~~
	~~$ export CXX=g++32~~

	~~You have to install compat-~~gcc-~~32 and compat-~~gcc~~-32-g++ , also http://www.tellurian.com.au/whitepapers/multiplegcc.php may be ho help~~		A: Better use mybe "gcc -V" the build in function of gcc to switch versions

	Now we download gcc, binuitils and newlib, which can be found at:		Now we download gcc, binuitils and newlib, which can be found at:
Line 257:		Line 265:
	Now, remember to undo that symlink:		Now, remember to undo that symlink:

	sudo rm /usr/bin/gcc		sudo unlink /usr/bin/gcc
	sudo ln -s /usr/bin/gcc-4.4 /usr/bin/gcc # Change 4.4 by your most recent gcc compiler, see ls -l /usr/bin/gcc-*		sudo ln -s /usr/bin/gcc-4.4 /usr/bin/gcc # Change 4.4 by your most recent gcc compiler, see ls -l /usr/bin/gcc-*

Openuas: /* About gcc versions */

2010-08-05T14:03:06Z

About gcc versions

← Older revision		Revision as of 08:03, 5 August 2010
Line 199:		Line 199:
	* I don't know if this affects (know nothing about arm7 actually), but there's a bug on gcc 3 arm7 cross-compilers described at [http://www.openhardware.net/Embedded_ARM/Toolchain/#gcc3bug http://www.openhardware.net/Embedded_ARM/Toolchain/#gcc3bug].		* I don't know if this affects (know nothing about arm7 actually), but there's a bug on gcc 3 arm7 cross-compilers described at [http://www.openhardware.net/Embedded_ARM/Toolchain/#gcc3bug http://www.openhardware.net/Embedded_ARM/Toolchain/#gcc3bug].
	* Paparazzi-bin build process (making deb package) compiles some files with the cross compiler, and the switch -mapcs-32. That switch is deprecated in gcc version 4, so if we want to make a compiler that make the paparazzi-bin package compile, we need to use a gcc version 3 compiler.		* Paparazzi-bin build process (making deb package) compiles some files with the cross compiler, and the switch -mapcs-32. That switch is deprecated in gcc version 4, so if we want to make a compiler that make the paparazzi-bin package compile, we need to use a gcc version 3 compiler.
	* For 64bit systems version 4 compilers for arm can be downloaded from the [http://www.gnuarm.~~org~~ gnuarm] project. As told above, they don't support the -mapcs-32 switch. Version 3 compilers from gnuarm project doesn't have that switch enabled too.		* For 64bit systems version 4 compilers for arm can be downloaded from the [http://www.gnuarm.com gnuarm] project. As told above, they don't support the -mapcs-32 switch. Version 3 compilers from gnuarm project doesn't have that switch enabled too.

	I'm sure there are tons of sites where you can download an arm7 cross-compiler which works well with that LPC2148 device. But my goal here is to build one that can after be used to build the paparazzi-bin deb package, so there's a need for that -mapcs-32 switch. Based on this, i decided to make the same versions as in the paparazzi debian repository, that's:		I'm sure there are tons of sites where you can download an arm7 cross-compiler which works well with that LPC2148 device. But my goal here is to build one that can after be used to build the paparazzi-bin deb package, so there's a need for that -mapcs-32 switch. Based on this, i decided to make the same versions as in the paparazzi debian repository, that's:

Openuas: /* Toolchain compilation */

2010-08-01T21:52:32Z

Toolchain compilation

← Older revision		Revision as of 15:52, 1 August 2010
Line 232:		Line 232:

	QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?		QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?
	A: Change your CC environmental variable to the version you want, as $ export CC=gcc-3.4
			A: Change your CC environmental variable to the version you want, as in $ export CC=gcc-3.4
			Before compiling a program, in the same terminal in which you are going to run configure/make, type:
			Code:

			$ export CC=gcc32
			$ export CXX=g++32

			You have to install compat-gcc-32 and compat-gcc-32-g++ , also http://www.tellurian.com.au/whitepapers/multiplegcc.php may be ho help

	Now we download gcc, binuitils and newlib, which can be found at:		Now we download gcc, binuitils and newlib, which can be found at:

Openuas: /* Toolchain compilation */

2010-08-01T21:48:00Z

Toolchain compilation

← Older revision		Revision as of 15:48, 1 August 2010
Line 232:		Line 232:

	QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?		QUESTION: Does anyone know how to specify the compiler to use instead of this dirty thing?
			A: Change your CC environmental variable to the version you want, as $ export CC=gcc-3.4

	Now we download gcc, binuitils and newlib, which can be found at:		Now we download gcc, binuitils and newlib, which can be found at:

Roirodriguez: /* Debian packages */

2010-02-05T01:03:22Z

Debian packages

← Older revision		Revision as of 19:03, 4 February 2010
Line 172:		Line 172:

	And now you can run dpkg-buildpackage to generate your deb packages. You can find mine (amd64), and modified sources (dpatch modifications described here, changelog file) in [http://imasdtrade.x10hosting.com/paparazzi/ http://imasdtrade.x10hosting.com/paparazzi/].		And now you can run dpkg-buildpackage to generate your deb packages. You can find mine (amd64), and modified sources (dpatch modifications described here, changelog file) in [http://imasdtrade.x10hosting.com/paparazzi/ http://imasdtrade.x10hosting.com/paparazzi/].

			NOTE: This solution is to avoid modifying the original sources. A proper patch for the original sources would be one that checks if the system is a 64bit system, and if so set FPIC env variable, the following code at the begining of the Makefile would be ok (taken from ivy-c Makefile):

			PERHAPS64 := $(shell uname -m \| perl -ne "print /64/ ? '64' : '';")
			ifeq ($(PERHAPS64), "64")
			FPIC=
			else
			FPIC=-fPIC
			endif

			And then let the rule to compile all .c and .o files be like the following:

			.c.o :
			$(CC) -Wall -c $(FPIC) $(OCAMLINC) $(GLIBINC) $<

	=== Paparazzi-arm7 packages ===		=== Paparazzi-arm7 packages ===

Roirodriguez: /* Debian packages */

2010-02-05T00:37:31Z

Debian packages

← Older revision		Revision as of 18:37, 4 February 2010
Line 321:		Line 321:
	==== Debian packages ====		==== Debian packages ====

	The package generated here don't fully work (read at the end to see what fails), so don't use it but for testing purposes.		The package generated here don't fully work (read at the end to see what fails), so don't use it but for testing purposes. The compiled sources compiled like above works well.

	First of all, don't simply run dpkg-buildpackage, there's a Makefile rule instead! Just run:		First of all, don't simply run dpkg-buildpackage, there's a Makefile rule instead! Just run:
Line 397:		Line 397:
	make: Leaving directory `/usr/share/paparazzi'		make: Leaving directory `/usr/share/paparazzi'

	Inspecting my /home/roi/paparazzi directory and comparing to /usr/share/paparazzi i can see that not all files where copied when paparazzi was first run. The curious thing is that if i run ./paparazzi from the sources dir instead executing the installed one (/usr/bin) everything works ok...		Inspecting my /home/roi/paparazzi directory and comparing to /usr/share/paparazzi i can see that not all files where copied when paparazzi was first run. The curious thing is that if i run ./paparazzi from the sources dir instead executing the installed one (/usr/bin) everything works ok (PAPARAZZI_SRC is taken as PAPARAZZI_HOME this way)...

	QUESTION: Any ideas on why? I'm sure i can solve it by myself, but if anybody knows...		QUESTION: Any ideas on why? I'm sure i can solve it by myself, but if anybody knows...

Roirodriguez: /* Debian packages */

2010-02-05T00:33:21Z

Debian packages

← Older revision		Revision as of 18:33, 4 February 2010
Line 320:		Line 320:

	==== Debian packages ====		==== Debian packages ====

			The package generated here don't fully work (read at the end to see what fails), so don't use it but for testing purposes.

	First of all, don't simply run dpkg-buildpackage, there's a Makefile rule instead! Just run:		First of all, don't simply run dpkg-buildpackage, there's a Makefile rule instead! Just run:
Line 386:		Line 388:
	BUILD /home/roi/paparazzi/var/MJ5/airframe.h		BUILD /home/roi/paparazzi/var/MJ5/airframe.h
	##################################################		##################################################

	AIRFRAME MODEL: MJ5		AIRFRAME MODEL: MJ5

	##################################################		##################################################
	make[1]: *** No rule to make target `/home/roi/paparazzi/conf/modules/*.xml', needed by `/home/roi/paparazzi/var/MJ5/modules.h'. Stop.		make[1]: *** No rule to make target `/home/roi/paparazzi/conf/modules/*.xml', needed by `/home/roi/paparazzi/var/MJ5/modules.h'. Stop.

Roirodriguez: /* Debian packages */

2010-02-05T00:31:49Z

Debian packages

@@ Line 338: / Line 338: @@
 QUESTION: Where am i supposed to get that map file from? Or does that line from Makefile.install need to be removed from the repository?
-If now we run '''make deb'''  again, the error is now:
+If now we run ''make deb''  again, the error is now:
   dpkg-gencontrol: error: current host architecture 'amd64' does not appear in package's architecture list (i386)
@@ Line 348: / Line 348: @@
   cp changelog.lenny changelog.karmic
-Then i edited debian/control.karmic and changed the line saying '''Architecture: i386''' by '''Architecture: any'''. Now i run:
+Then i edited debian/control.karmic and changed the line saying ''Architecture: i386'' by ''Architecture: any''. Now i run:
-  DISTRO="karmic" make deb
+  make DISTRO="karmic" deb
 (See deb rule in the makefile to see how the DISTRO env variable is used).

Roirodriguez: /* Debian packages */

2010-02-04T23:50:53Z

Debian packages

@@ Line 330: / Line 330: @@
   install: no se puede efectuar `stat' sobre «var/maps/trtqtttqtsrrtstq*.jpg»: No existe el fichero ó directorio
   install: no se puede efectuar `stat' sobre «var/maps/trtqtttqtsrrttsr*.jpg»: No existe el fichero ó directorio
-make[3]: *** [install_data] Error 1
+ make[3]: *** [install_data] Error 1