sparc 4.11 tools build failure on CentOS 6.x
Chris Johns
chrisj at rtems.org
Wed Jan 29 03:38:25 UTC 2014
On 29/01/2014 3:46 am, Joel Sherrill wrote:
> Hi
>
> Not sure what broke recently but something went wrong. :(
>
> Can anyone build sparc-rtems4.11 tools with the rtems-source-builder
> head?
Yes on FreeBSD 9 and on MacOS Mavrick ....
Build Set: Time 0:08:46.537755
>
> /bin/sh ../../gcc-4.8.2/gcc/mkconfig.sh bconfig.h
> /usr/bin/g++ -O2 -pipe
> -I/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/tmp/sb-joel/4.11/rtems-sparc/home/joel/rtems-4.11-work/tools/include
> -c -g -O2 -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -fno-exceptions
> -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wwrite-strings
> -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long
> -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H
> -DGENERATOR_FILE -I. -Ibuild -I../../gcc-4.8.2/gcc
> -I../../gcc-4.8.2/gcc/build -I../../gcc-4.8.2/gcc/../include
> -I../../gcc-4.8.2/gcc/../libcpp/include
> -I/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/sparc-rtems4.11-gcc-4.8.2-newlib-2.1.0-1/build/./gmp
> -I/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/sparc-rtems4.11-gcc-4.8.2-newlib-2.1.0-1/gcc-4.8.2/gmp
> -I/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/sparc-rtems4.11-gcc-4.8.2-newlib-2.1.0-1/build/./mpfr
> -I/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/sparc-rtems4.11-gcc-4.8.2-newlib-2.1.0-1/gcc-4.8.2/mpfr
> -I/home/joel/rtems-4.11-work/rtems-source-builder/rtems/build/sparc-rtems4.11-gcc-4.8.2-newlib-2.1.0-1/gcc-4.8.2/mpc/src
> -I../../gcc-4.8.2/gcc/../libdecnumber
> -I../../gcc-4.8.2/gcc/../libdecnumber/dpd -I../libdecnumber
> -I../../gcc-4.8.2/gcc/../libbacktrace \
> -DBASEVER="\"4.8.2\"" -DDATESTAMP="\" 20131016\"" \
> -DREVISION="\"\"" \
> -DDEVPHASE="\" (RTEMS
> 4.11-RSB(2be445d2aafae21849c5d626b3787e2ab1ac846b)-1,gcc-4.8.2/newlib-2.1.0)\""
Same git hash I am using.
> -DPKGVERSION="\"(GCC) \"" \
> -DBUGURL="\"<http://gcc.gnu.org/bugs.html>\"" -o build/version.o
> ../../gcc-4.8.2/gcc/version.c
> {standard input}: Assembler messages:
> {standard input}:33: Error: unknown pseudo-op: `.value'
> {standard input}:183: Error: unknown pseudo-op: `.value'
>
Anything in your path that could up set up things ?
Do the installed RPMs verify ?
Chris
More information about the devel
mailing list