alphaWorks > Forums > Full System Simulator for IBM PowerPC 970 >

compile error under feisty fawn


Search for within

My developerWorks

Welcome, Guest

	Sign in or register

Reply to this Thread

Post New Thread

Watch list

Forum settings

Help

	Replies: 1 - Pages: 1 - Last Post: Jan 17, 2009 4:55 AM Last Post By: curiousDeveloper	Threads: [ Previous \| Next ]

Posts: 1
Registered: Oct 15, 2007 11:39:21 AM

compile error under feisty fawn
Posted: Oct 15, 2007 01:11:24 PM

I don't know if its problem that i use feisty fawn. I get the following error message:
/ibmsim/toolchain/src/crosstool/build/powerpc-750-linux-gnu/gcc-4.1.0-glibc-2.3.6/build-glibc/csu/version-info.h:2:1: missing terminating " character
/ibmsim/toolchain/src/crosstool/build/powerpc-750-linux-gnu/gcc-4.1.0-glibc-2.3.6/build-glibc/csu/version-info.h:3:1: missing terminating " character

The error has occoured already by compiling the toolchain.
The file version-info.h looks like:

"Compiled on a Linux 2.6.12 system on 2007-10-15.\n"
"Available extensions:
"
" GNU libio by Per Bothner\n"
" crypt add-on version 2.1 by Michael Glad and others\n"
" linuxthreads-0.10 by Xavier Leroy\n"
" BIND-8.2.3-T5B\n"
" libthread_db work sponsored by Alpha Processor Inc\n"
" NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk\n"
" software FPU emulation by Richard Henderson, Jakub Jelinek and others\n"

Exist any solution?

curiousDeveloper

Posts: 4
Registered: Jan 16, 2009 02:18:56 AM

Re: compile error under feisty fawn
Posted: Jan 17, 2009 04:55:13 AM

in response to: 's post

This affected me as well as I run Ubuntu Hardy Heron. This webpage http://matrix108.wordpress.com/2007/11/28/arm-toolchain/ solved the problem though. I quote:

The Ubuntu shell is not bash by default! Instead it is linked to something called dash. Just make sure you relink /bin/sh to bash instead of dash. No idea when they did this, but I found that out after encountering this maddening error, pointing to some header files during the build:

missing terminating ” character.

I followed the above advice by making a symbolic link from /bin/sh -> /bin/sh.distrib and that error went away.

Pages: 1

Back to Thread List

Threads: [ Previous | Next ]

Update your My developerWorks profile and start connecting with others.