Re: gdbserver - manually modify Makefile

Ran Shalit <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <CAJ2oMhJ9yBEVk6sqwz=2aWCOD8_vbBo82vjpFiWKM7aKxFpJww@mail.gmail.com>
On Fri, Aug 14, 2015 at 12:58 AM, Pedro Alves <[email protected]> wrote:
> On 08/13/2015 09:50 PM, Ran Shalit wrote:
>> Hello,
>>
>> I've  cross compile  gdbserver according to wiki in:
>> https://sourceware.org/gdb/wiki/BuildingCrossGDBandGDBserver
>> ubuntu@ubuntu-laptop:~/gdb-7.9.1/gdb/gdbserver$ sudo ./configure
>> --host=powerpc-buildroot-linux-gnu --disable-werror
>
> You should not need sudo, nor --disable-werror.
>
>>
>> But on doing :
>> make
>> I've noticed that it uses the host gcc instead of the cross-compiler gcc.
>> Only after manually modifying the Makefie with
>> CC = powerpc-buildroot-linux-gnu-gcc
>> instead of
>> CC = gcc
>> It was cross compiling as expected.
>>
>
> Open the config.log file in the build directory, and look for something
> that looks like this:
>
> configure:2558: checking for powerpc-buildroot-linux-gnu-gcc
>
> The following lines should look something like this:
>
> configure:2574: found /path/to/whatever/bin/powerpc-buildroot-linux-gnu-gcc
> configure:2585: result: powerpc-buildroot-linux-gnu-gcc
> configure:2854: checking for C compiler version
> configure:2863: powerpc-buildroot-linux-gnu-gcc --version >&5
>
> But in your case, "result" is probably "gcc".  If configure doesn't
> find $host-gcc, then it'll default to "gcc".  Most likely, you don't
> have powerpc-buildroot-linux-gnu-gcc in the PATH.  Make sure
> it is in the PATH, and that you can execute it (e.g., try
> $ powerpc-buildroot-linux-gnu-gcc -v), and start over.
>
> Let me know how it went.
>
> Thanks,
> Pedro Alves
>

Hi Pedro,

Thanks for the feedback.
You were correct about the PATH, that solved the issue !

But I still need the --disable-werror, otherwise it stops build on
warning (treated as error).

Regards,
Ran
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.