canadian cross problems

canadian cross problems

[Axel Kittenberger]

This is proparly an easy problem, as I'm a complete beginner :)

I'm trying to compile a mingw->powerpc cross-compiler.

After some quarrals I finally managed to make my native(linux)->mingw
compiler. (I'm using 2.95.2-1)

Tring to cross compile the mingw->powerpc the make file stops in /gcc/gcc
with
-----------------------------------------------------
./gencheck > tmp-check.h
/bin/sh: ./gencheck: cannot execute binary file
make: *** [s-check] Error 126                         
-----------------------------------------------------

Sure it has to be that way, he cannot execute gencheck as it is a windows
executable.

However knowing the problem seems not to be enough :o)
What can I do against him trying to exectue this?

-- 
Sent through GMX FreeMail - http://www.gmx.net

Re: canadian cross problems

[Alexandre Oliva]

On Jan  4, 2001, Axel Kittenberger <Anshil@gmx.net> wrote:

> After some quarrals I finally managed to make my native(linux)->mingw
> compiler. (I'm using 2.95.2-1)

> Tring to cross compile the mingw->powerpc the make file stops in /gcc/gcc
> with

How did you configure this Canadian cross?  Did you specify all of
--build, --host and --target?  If you miss any of these, configure
will not realize it's a Canadian cross and will fail to enable the use
of a native compiler to compile programs that are supposed to run on
the build machine.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

canadian cross problems 2

[Axel Kittenberger]

Oh that explains it :-)

I didn't give him a --build, I simply modified my path so that I grabbed
him away the native compiler replacing it with the cross compiler, wasn't
aware that when cross-compiling gcc you still need the native compiler :-)

This time I configured it with:
--------------------------------------------------------
../source/gcc-2.95.2/configure --target=ppc-unknown-elf --prefix=~/gcc-pcc
--build=i386-mingw32 --host=i686-pc-linux-gnu
--------------------------------------------------------
However I get following error condidition

He now tries to run i686-pc-linux-gnu-* instead of directly the native
compiler/binutils, however some quick symlinks resolve that problem :o)

Unfortunally I get now following error:
--------------------------------------------------------
rm -f SYSCALLS.c tmp-SYSCALLS.s
cat ../../source/gcc-2.95.2/gcc/sys-types.h
../../source/gcc-2.95.2/gcc/sys-protos.h > SYSCALLS.c
ppc-unknown-elf-gcc -DCROSS_COMPILE -DIN_GCC -DHAIFA    -g -O2 -I./include
    -I. -I../../source/gcc-2.95.2/gcc -I../../source/gcc-2.95.2/gcc/config
-I../../source/gcc-2.95.2/gcc/../include \
  -aux-info SYSCALLS.c.X -S -o tmp-SYSCALLS.s SYSCALLS.c
make[1]: ppc-unknown-elf-gcc: Command not found                           
                          
--------------------------------------------------------

Why does he now try to execute the cross target?

> On Jan  4, 2001, Axel Kittenberger <Anshil@gmx.net> wrote:
> 
> > After some quarrals I finally managed to make my native(linux)->mingw
> > compiler. (I'm using 2.95.2-1)
> 
> > Tring to cross compile the mingw->powerpc the make file stops in
> /gcc/gcc
> > with
> 
> How did you configure this Canadian cross?  Did you specify all of
> --build, --host and --target?  If you miss any of these, configure
> will not realize it's a Canadian cross and will fail to enable the use
> of a native compiler to compile programs that are supposed to run on
> the build machine.
> 
> -- 
> Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist    *Please* write to mailing lists, not to me
> 

-- 
Sent through GMX FreeMail - http://www.gmx.net

RE: canadian cross problems 2

[Axel Kittenberger]

Umm, thing already have it :o)

I believe I mismatched build and host... 
I suppose build is the machine where I create the compiler
and host the one where it should run on?

However the stones do not end so fast :o)
-----------------------------------------------------------------
i686-pc-linux-gnu-gcc -DCROSS_COMPILE -DIN_GCC -DHAIFA    -g -O2 
-DHAVE_CONFIG_H  -o cccp.exe cccp.o cexp.o intl.o prefix.o version.o  mbchar.o 
obstack.o
  -ladvapi32 ../libiberty/libiberty.a
/usr/bin/ld: cannot open -ladvapi32: No such file or directory
collect2: ld returned 1 exit status                                       
                       
-----------------------------------------------------------------

I am missing libadvapi32? Is this a libiberty sub library?
Or did I do something wrong causing it not to be build...

------------------------
--- Original Message ---
Date: Fri, 5 Jan 2001 09:22:25 +0100 (MET)
From: Axel Kittenberger <Anshil@gmx.net>
To: gcc-help@gcc.gnu.org
Subject: canadian cross problems 2

> Oh that explains it :-)
> 
> I didn't give him a --build, I simply modified my path so that I grabbed
> him away the native compiler replacing it with the cross compiler,
> wasn't
> aware that when cross-compiling gcc you still need the native compiler
> :-)
> 
> This time I configured it with:
> --------------------------------------------------------
> ../source/gcc-2.95.2/configure --target=ppc-unknown-elf
> --prefix=~/gcc-pcc
> --build=i386-mingw32 --host=i686-pc-linux-gnu
> --------------------------------------------------------
> However I get following error condidition
> 
> He now tries to run i686-pc-linux-gnu-* instead of directly the native
> compiler/binutils, however some quick symlinks resolve that problem :o)
> 
> Unfortunally I get now following error:
> --------------------------------------------------------
> rm -f SYSCALLS.c tmp-SYSCALLS.s
> cat ../../source/gcc-2.95.2/gcc/sys-types.h
> ../../source/gcc-2.95.2/gcc/sys-protos.h > SYSCALLS.c
> ppc-unknown-elf-gcc -DCROSS_COMPILE -DIN_GCC -DHAIFA    -g -O2
> -I./include
>     -I. -I../../source/gcc-2.95.2/gcc
> -I../../source/gcc-2.95.2/gcc/config
> -I../../source/gcc-2.95.2/gcc/../include \
>   -aux-info SYSCALLS.c.X -S -o tmp-SYSCALLS.s SYSCALLS.c
> make[1]: ppc-unknown-elf-gcc: Command not found                         
>  
>                           
> --------------------------------------------------------
> 
> Why does he now try to execute the cross target?
> 
> > On Jan  4, 2001, Axel Kittenberger <Anshil@gmx.net> wrote:
> > 
> > > After some quarrals I finally managed to make my
> native(linux)->mingw
> > > compiler. (I'm using 2.95.2-1)
> > 
> > > Tring to cross compile the mingw->powerpc the make file stops in
> > /gcc/gcc
> > > with
> > 
> > How did you configure this Canadian cross?  Did you specify all of
> > --build, --host and --target?  If you miss any of these, configure
> > will not realize it's a Canadian cross and will fail to enable the use
> > of a native compiler to compile programs that are supposed to run on
> > the build machine.
> > 
> > -- 
> > Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> > Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
> > CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
> > Free Software Evangelist    *Please* write to mailing lists, not to me
> > 
> 
> -- 
> Sent through GMX FreeMail - http://www.gmx.net
> 

-- 
Sent through GMX FreeMail - http://www.gmx.net

Re: canadian cross problems 2

[Alexandre Oliva]

On Jan  5, 2001, Axel Kittenberger <Anshil@gmx.net> wrote:

> --------------------------------------------------------
> ../source/gcc-2.95.2/configure --target=ppc-unknown-elf --prefix=~/gcc-pcc
> --build=i386-mingw32 --host=i686-pc-linux-gnu
> --------------------------------------------------------

You need a cross-compiler for the target hosted on the build machine
before you can build a canadian cross for the same target.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

'nother cross question

[Axel Kittenberger]

...umm sorry if I'm starting to be annoying....

Okay, didn't realize that I really need 3 compilers hosted on the same
machine to do a canadion croos.

I'm a little confused regarding the target headers....
Suppose my target is OS-less, 
and in example I don't require profile support or similar extension stuff
that relies on an OS or stdio. 

What do I do in this case?

- Axel

-- 
Sent through GMX FreeMail - http://www.gmx.net

'nother cross question-2

[Axel Kittenberger]

Okay from looking at sources I guess adding the compiler flag

-Dinhibit_libc

does what I want, or?

Gcc itself compiles fine withi t,

However libiberty still is not happy
(choose-temp.c wants to have an os)

I'm not sure what libiberty plays for a role. Does gcc rely on it?
Can I completly scrap it away for my purposes?

- Axel

-- 
Sent through GMX FreeMail - http://www.gmx.net

Re: 'nother cross question

[Alexandre Oliva]

On Jan  5, 2001, Axel Kittenberger <Anshil@gmx.net> wrote:

> I'm a little confused regarding the target headers....
> Suppose my target is OS-less, 
> and in example I don't require profile support or similar extension stuff
> that relies on an OS or stdio. 

> What do I do in this case?

Use newlib, for example.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me