Your CC was not properly setup.
You need to use the compiler on you host pc, for example, if you are
compiling gdb under x86 for powerpc, your cc should be your local gcc.
HTH.
Regards,
Simon


On Thu, Jan 19, 2012 at 2:40 AM, Venkateswara Rao Yenuganti <
venkateswara.yenuga...@aricent.com> wrote:

>  Hi,****
>
> I am trying to do cross compile gdb6.6.I downloaded the tar file and I
> untared it.after that I have given the following commands.****
>
> ** **
>
> ./configure --target=powerpc-linux CC=powerpc-linux-gnu-gcc export
> CC=powerpc-linux-gnu-gcc make****
>
> ** **
>
> After make I am getting the following errors****
>
> ** **
>
> make[1]: Entering directory `/home/venkat/gdbtools/gdb-6.6'****
>
> Configuring in ./libiberty****
>
> configure: loading cache ./config.cache****
>
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for makeinfo... /home/venkat/gdbtools/gdb-6.6/missing makeinfo
> --split-size=5000000****
>
> configure: WARNING:****
>
> *** Makeinfo is missing. Info documentation will not be built.****
>
> checking for perl... perl****
>
> checking build system type... Invalid configuration
> `CC=powerpc-linux-gnu-gcc': machine `CC=powerpc-linux-gnu' not recognized*
> ***
>
> configure: error: /bin/sh .././libiberty/../config.sub
> CC=powerpc-linux-gnu-gcc failed****
>
> make[1]: *** [configure-libiberty] Error 1****
>
> make[1]: Leaving directory `/home/venkat/gdbtools/gdb-6.6'****
>
> make: *** [all] Error 2****
>
> ** **
>
> ** **
>
> ** **
>
> my os is : Linux localhost.localdomain 2.6.35.6-45.fc14.i686 #1 SMP Mon
> Oct 18 23:56:17 UTC 2010 i686 i686 i386 GNU/Linux****
>
> ** **
>
> my cross compiler is : gcc version 4.5.1 (Sourcery G++ Lite 2010.09-55)***
> *
>
> ** **
>
> Thanks in advance****
>
> Venkateswararao ****
>
> ** **
>
>
>
>
>
> ===============================================================================
> Please refer to http://www.aricent.com/legal/email_disclaimer.html
> for important disclosures regarding this electronic communication.
>
> ===============================================================================
>

Reply via email to