This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: canadian cross problems 2


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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]