Building 4.10

[Yann Sionneau]

Le 11/02/11 19:07, Claus, Ric a écrit :
> I am trying to build RTEMS 4.10 for use by a cluster of computers.  This means that it and its associated (gnu) tools are to be installed on an NFS served partition and thus the supplied prebuilt packages won't do.  Instead, I've been grabbing files from http://www.rtems.org/ftp/pub/rtems/SOURCES/4.10/ and http://www.rtems.org/ftp/pub/rtems/4.10.0/.  I have been following a recipe similar to that given at http://www.rtems.com/wiki/index.php/Building_the_RTEMS_toolset_on_Ubuntu (I have a RHEL 5 environment) which has worked well for me when building 4.9.4 and 4.11, but 4.10 is giving me trouble, so I have a couple of questions.
>
> - I presume I'm supposed to use the sources in the release (4.10) directory and not those in the SOURCES directory.  Correct?
I've never built the 4.10, but for the 4.11 I take the sources in the 
SOURCES directory.
>
> - A number of packages have more than one patch (.diff) file.  Are they all to be applied, or does the most recent one include all the older patches?
I've always applied only the most recent patch and it worked well (for 
4.11 again).
>
> - Can someone help me to understand why gcc builds fine for quite a while and then suddenly blows up with:
> gcc -c  -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual -Wold-style-definition -Wc++-compat -Wmissing-format-attribute   -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../gcc-4.4.5/gcc -I../../gcc-4.4.5/gcc/build -I../../gcc-4.4.5/gcc/../include -I../../gcc-4.4.5/gcc/../libcpp/include -I/reg/lab1/home/claus/ctk/tools/b-gcc/./gmp -I/reg/lab1/home/claus/ctk/tools/gcc-4.4.5/gmp -I/reg/lab1/home/claus/ctk/tools/b-gcc/./mpfr -I/reg/lab1/home/claus/ctk/tools/gcc-4.4.5/mpfr  -I../../gcc-4.4.5/gcc/../libdecnumber -I../../gcc-4.4.5/gcc/../libdecnumber/dpd -I../libdecnumber    -o build/genmodes.o ../../gcc-4.4.5/gcc/genmodes.c
> /tmp/cct9SX9s.s: Assembler messages:
> /tmp/cct9SX9s.s:17: Error: Unrecognized opcode: `pushl'
> /tmp/cct9SX9s.s:19: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:21: Error: Unrecognized opcode: `subl'
> /tmp/cct9SX9s.s:24: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:26: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:28: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:31: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:34: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:35: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:38: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:39: Error: syntax error; found `(' but expected `,'
> /tmp/cct9SX9s.s:39: Error: junk at end of line: `(%edx)'
> /tmp/cct9SX9s.s:40: Error: Unrecognized opcode: `jbe'
> /tmp/cct9SX9s.s:44: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:47: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:48: Error: Unrecognized opcode: `movl'
> /tmp/cct9SX9s.s:49: Error: Unrecognized opcode: `movl'
> [...]
>
> 	Thanks,
> 			Ric Claus
>
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users