Issues with compiling RTEMS 4.10.2 with Gaisler drivers 1.2.11 on Ubuntu 13.04

Thu Aug 8 10:01:46 UTC 2013

Hi,

I am fairly new to RTEMS and want to understand how to build RTEMS
4.10.2 with Gaisler drivers 1.2.11 for SPARC on Ubuntu 13.04 from
source. What I did up to now is:

* I prepared a dedicated user and directory structure for all my RTEMS
work on a clean Ubuntu 13.04 x64 installation. I want all RTEMS-related
files to reside in /home/rtems/rtems_base (no files outside this path).

* autoconf 2.68 and automake 1.11.1 have been compiled and installed.

* Expat 2.1.0 has been compiled and installed, as well as binutils 2.20.1.

* GCC 4.4.7 has been patched witch the patches
	4.10/gcc/gcc-core-4.4.7-rtems4.10-20120314.diff
	4.10/gcc/gcc-g++-4.4.7-rtems4.10-20120314.diff
   from the Git repository git://git.rtems.org/rtems-tools.git and
newlib 1.18.0, patched with
	4.10/newlib/newlib-1.18.0-rtems4.10-20110518.diff
   has been linked into the GCC sources. Finally, GCC has been compiled
and installed.

* GDB 7.3.1 has been patched with
	4.10/gdb/gdb-7.3.1-rtems4.10-20120918.diff
   and has been compiled and installed.

If necessary, I can provide you a document with all steps I did since
the clean Ubuntu install.

When I configure RTEMS and run a 'make all' now, I will get the
following error:

	configure: error: in
`/home/rtems/rtems_base/build/arch/sparc-rtems4.10/rtems-4.10.2-gaisler-1.2.11/sparc-rtems4.10/c/erc32':
	configure: error: C compiler cannot create executables
	See `config.log' for more details

'config.log' states the following:

    configure:3438: sparc-rtems4.10-gcc -V >&5
    sparc-rtems4.10-gcc: '-V' option must have argument
    configure:3449: $? = 1
    configure:3438: sparc-rtems4.10-gcc -qversion >&5
    sparc-rtems4.10-gcc: unrecognized option '-qversion'
    sparc-rtems4.10-gcc: no input files
    configure:3449: $? = 1
    configure:3469: checking whether the C compiler works
    configure:3491: sparc-rtems4.10-gcc -mcpu=cypress -O2 -g
conftest.c  >&5
    /tmp/ccmy1mrr.s: Assembler messages:
    /tmp/ccmy1mrr.s:13: Error: unrecognized symbol type ""
    /tmp/ccmy1mrr.s:14: Error: unknown pseudo-op: `.proc'
    /tmp/ccmy1mrr.s:21: Error: bad register name `%o7+8'
    /tmp/ccmy1mrr.s:22: Error: bad register name `%o0'
    /tmp/ccmy1mrr.s:28: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:29: Error: unknown pseudo-op: `.uahalf'
    /tmp/ccmy1mrr.s:30: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:33: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:35: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:36: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:37: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:38: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:39: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:42: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:45: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:46: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:47: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:109: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:110: Error: unknown pseudo-op: `.uahalf'
    /tmp/ccmy1mrr.s:111: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:112: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:113: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:115: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:117: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:118: Error: unknown pseudo-op: `.uahalf'
    /tmp/ccmy1mrr.s:119: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:122: Error: unknown pseudo-op: `.uahalf'
    /tmp/ccmy1mrr.s:123: Error: unknown pseudo-op: `.uahalf'
    /tmp/ccmy1mrr.s:124: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:125: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:126: Error: unknown pseudo-op: `.uaword'
    /tmp/ccmy1mrr.s:127: Error: unknown pseudo-op: `.uaword'
    configure:3495: $? = 1
    configure:3533: result: no
    configure: failed program was:
    | /* confdefs.h */
    | #define PACKAGE_NAME "rtems-c-src"
    | #define PACKAGE_TARNAME "rtems-c-src"
    | #define PACKAGE_VERSION "4.10.2"
    | #define PACKAGE_STRING "rtems-c-src 4.10.2"
    | #define PACKAGE_BUGREPORT "http://www.rtems.org/bugzilla"
    | #define PACKAGE_URL ""
    | /* end confdefs.h.  */
    |
    | int
    | main ()
    | {
    |
    |   ;
    |   return 0;
    | }
    configure:3538: error: in
`/home/rtems/rtems_base/build/arch/sparc-rtems4.10/rtems-4.10.2-gaisler-1.2.11/sparc-rtems4.10/c/erc32':
    configure:3540: error: C compiler cannot create executables
    See `config.log' for more details

Now I am stuck, because I have no idea whats the reason for this error
is. It is also unclear for me why 'sparc-rtems4.10-gcc -V' outputs an
error and whether this is expected or not.

So I hope somebody can help me to solve this problem. Thank you in advance.

Kind regards,
René
-- 

Sincerely yours,

M.Eng. *René Schwarz*

	German Aerospace Center (DLR)
	Member of the Helmholtz-Association

	| Institute of Space Systems
	| Guidance, Navigation and Control Systems, Avionics (RY-GNC)

	Room 2.10 · Robert-Hooke-Str. 7 · DE-28359 Bremen
	Phone: +49-(0)421-24420-1165 · Telefax: +49-(0)421-24420-1120
	E-Mail: rene.schwarz at dlr.de · Internet: http://www.DLR.de/irs/en/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://lists.rtems.org/pipermail/users/attachments/20130808/9f41dd90/attachment.bin>