RE: Cross-compiling ....

["Buddy Lott" <buddy_lott at hotmail dot com>]

I think I made it past my problems (except for a minor 1).

Here is what I did (after cleaning up from my previous attempts):

 

1)       Downloaded and installed cygwin
2)       Downloaded the binutils-2.13.tar  gcc-3.0.4.tar
newlib-1.9.0.tar.
3)       Mkdir m68k-elf && cd m68k-elf
4)       Untarred each file into m68k-elf
5)       Mkdir build
6)       Cd build
7)       ../binutils-2.13/configure -target=m68k-elf
8)       make all install
9)       ../gcc-3.0.4/configure -target=mk68k-elf -without-headers
-with-newlib
10)   make all-gcc install-gcc
11)   ../newlib-1.9.0/configure -target=mk68k-elf
12)   make all install
13)   ../gcc-3.0.4/configure -target=m68k-elf -with-newlib
14)   make all install

 
The only real difference (from previous attempts) was adding
"-with-newlib" to step 13.  I don't remember seeing this anywhere I
looked.

I repeated the process with -target=m69k-coff and had mostly the same
success. The only error was with the install take on step 14. It
complained about files in /usr/local/bin/#inst.xxxx# (xxxx is some
number) not being found it. This was because the file actually had a
.exe extension added on it. Then the problem went mysteriously away. I
still have to test to make sure that the compiler works... but at least
I have the compiler.

I did the same series of steps (minus the "-with-newlib") on RedHat
Linux 7.3 and it worked there perfectly.


> -----Original Message-----
> From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org]
On
> Behalf Of Andrea Bocci
> Sent: Monday, August 19, 2002 5:50 PM
> To: Buddy Lott; gcc-help@gcc.gnu.org
> Subject: Re: Cross-compiling ....
> 
> 
> > I am trying to build a cross-compiler that goes from a pc running
> > windows 2000 to an embedded Motorola 68360 processor. I have failed
in
> > so many ways so far that I am about ready to give up.
> 
> From the mailing list, cross compiling is the most complex thing
people
> encounter when
> using GCC. At least,  the one a lot of people complain about as being
> badly documented
> and hard to make work.
> 
> So, my advices are 0.) Try again with GCC 3.2and the latest binutils
and
> newlib (guess
> you won't used glibc for an ambedded target...) 1.) Read all the
latest ML
> messages
> regarding cross-compiling with GCC. 2.) Have a good search on Google
for
> something
> like   GCC "cross compiler" coìnfiguration howto 3.) If everthing else
> fail, and you're
> really interested in making things work, mail me. I'm on holiday right
> now, and I'll be
> home by the first days of September. Then, one of the things in my
> todolist is to put up a
> good GCC working base, so I'll bebuilding it as a crosscompiler from
> cygwin for quite
> some architectures (linux to test it, the hpux, solaris and
someembedded
> chip). If I
> menage it, I'll send a (skeleton of) documentation to the ML, and if
the
> thing gets good,
> maybe it'll end online some where.
> 
> I guess that feedback from others trying to do this will be
invaluable,
> so, stay tuned :-)
> 
> I know this won't help much right now, but maybe you'll keep on trying
:-)
> fwyzard