Re: change just host of cross compiler

[Kai Ruottu <karuottu at mbnet dot fi>]

lazer1 wrote:

> I use a 68k Amiga  (m68k-unknown-amigaos),
>
> I wish to create a 68k Amiga hosted cross compiler for AROS,
>
> ie I just wish to change just the host to my machine of the 
> existing cross compiler, target remains identical,
>
> On the 68k Amiga I use a native gcc-2.95.3-4, and there is a full 
> suite of native build tools, make, sed, awk, etc,

 But is it really suitable as being your preferred build platform?

> I dont quite see where the existing Linux-host:AROS-target gcc source 
> enters the picture,

 In quite usual case one chooses the best available Unix-like platform
as the build platform, then creates crosstools for the other 'secondary'
not-so-Unix-like hosts. Then produces all the toolchains on that chosen
build platform using the crosstools...

 My choice as the build platform was Linux/x86 and the 'secondary' hosts
are DOS/DJGPP2, Windoze/Cygwin, Windoze/MinGW and Sparc/Solaris2.7 for
which I have created at least two toolchains per host. I have/had cross-
tools for BeOS/x86, OS2/emx, MIPS/SVR4, SCO Unix 3.2, SCO Xenix 2.3,
UnixWare 1.1, FreeBSD/x86, NetBSD/x86 etc. but haven't built any toolchains
for them for years... I never have had a cross toolchain for AmigaOS/m68k
but maybe I could find some insane reason for producing it...

 The existing crosscompiler comes into picture when producing your
AmigaOS-x-AROS crosscompiler on your possibly chosen Linux build
system...

> any advice on how I proceed?

 Hehheh, using a m68k platform to build... What 'm68k', how many MIPS?
Believe me, I wouldn't consider anything slower than a Pentium 120 MHz
as the build platform nowadays...

 If you have a > 1 GHz PC, who you can even think using something like
a 20 MHz m68020 as the build platform?  1.6 MIPS versus 1600 MIPS with
a Duron 1600 MHz...

 What becomes to a Linux-x-AmigaOS cross-toolchain, you maybe don't even
need to build it yourself, others have found out this being needed:

----------------------------- clip ---------------------------------
Hello,

On Wed, 28 Apr 2004 15:23:54 +0200
Gabriele Greco <gabry@amiga.org> wrote:

> Markus Heinz wrote:
>
> > I would like to know if it is possible to build a cross compiler
> > out of gcc and binutils which runs on i386-linux and produces
> > m68k-amigaos programs. Unfortunately I cannot find a list which
> > targets are supported by gcc/binutils. Is m68k-amigaos still
> > supported in the recent versions of gcc and binutils, and if not,
> > what are the last versions of both which supported this target? Has
> > anyone done this before?
>
> You could find a precompiled one at the following URL:
>
> http://www.lysator.liu.se/~lcs/files/gg-cross/
>
> It's compiled for an old red hat but works correctly also with a newer
> one or another distribution (using rpm2tgz or alien). In the site
> you'll find also the patches needed to build it AFAIK you can find
> also the needed patches for newer gccs at www.geekgadgets.org in the
> alpha directory.

Thank you very much. With the help of the tutorial at [1] I have managed
to build a working cross-compiler out of gcc 3.3.3.

[1] http://www.geekgadgets.org/docs/GG_8.html#SEC55

Best regards,

Markus

--
Visit my homepage: http://home.arcor.de/markusheinz/
----------------------------- clip ---------------------------------

> should I use the Linux-host:AROS-target sources in place of the 
> (gcc+gas+gld+binutils+gdb+newlib) suite in the FAQ

 Most probably this is the right choice. The Linux-x-AmigaOS doesn't
need to be from the same sources, you can think it being just another
kind of native GCC with which to produce other toolchains...

> the Canadian Cross scenario sounds too general for this scenario,

 What was suggested here, is just the Canadian cross, requiring three
different GCCs (for build, host and target), all hosted on the build
system for producing anything...

 The scheme goes:

 1. produce the toolchain for the primary (build) host
 2. produce the toolchain for all the secondary hosts. Cross-tools
    for the secondary hosts must pre-exist

 And you must handle the configury system as a stupid soldier for
which everything must be told exactly, never forget to tell what
the '--build=', '--host=' and '--target=' are...

Cheers, Kai



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com