Re: Building a Cross compiler for Cold Fire

[Michael Eager <eager at eagercon dot com>]

Rohit Arul Raj wrote:
> Hi all,
>
> i am trying to build a GCC Cross-compiler for Cold Fire on cygwin. The
> Source versions i am using are
>
> binutils 2.17
> gcc 4.1.1
> newlib 1.14
>
> The way in which i am building the tool chain
>
> - build/install binutils:
>  cd /binutil-2.17
>  ./configure --target=m68k-elf --prefix=/usr
>  make
>  make install

The general wisdom is to build in a different directory from
the source distribution (for both binutils and gcc):

  mkdir bin-build
  cd bin-build
  ../binutils-2.17/configure --target=m68k-elf --prefix=/usr
  make
  make install

> - build/install compiler
>  cd gcc-4.1.1
>  ./configure --target=m68k-elf --prefix=/usr
>  make LANGUAGE="C"

You probably also want --with-newlib.
Copy newlib-1.14/newlib into the gcc source directory.
The gcc build will pick up the correct include files
and build newlib.

Also --disable-libssp, because of a GCC bug.

> the native compiler i am using is  gcc 3.4.4 Cygwin-special
> my binutils built successfully.
> while building the compiler i am getting error while running make
> "compiler cannot generate output file"

This message is not about your host compiler.
It is generated when the build attempts to compile a program
using the cross compiler.  Look in config.log in the directory
in which the compile is run for information about the failure.

Often, when I get this kind of error, I will cd to the
build directory, set the PATH to include the binutils
install directory if necessary, and run the failing command.
I can then use -E or --print-search-paths or whatever to
figure out why the compiler cannot create an executable.

--
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077