From: Pedro Alves <palves@redhat.com>
To: Ran Shalit <ranshalit@gmail.com>, gdb <gdb@sourceware.org>
Subject: Re: gdbserver - manually modify Makefile
Date: Thu, 13 Aug 2015 21:58:00 -0000 [thread overview]
Message-ID: <55CD1308.3020602@redhat.com> (raw)
In-Reply-To: <CAJ2oMh+5j+Rk7s0uH=Og7jaDmtrAQp2UDCdaM4rMhQe3L5Dt5A@mail.gmail.com>
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
next prev parent reply other threads:[~2015-08-13 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 20:50 Ran Shalit
2015-08-13 20:53 ` Orlando Arias
2015-08-13 21:58 ` Pedro Alves [this message]
2015-08-13 22:26 ` Ran Shalit
2015-08-14 8:57 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55CD1308.3020602@redhat.com \
--to=palves@redhat.com \
--cc=gdb@sourceware.org \
--cc=ranshalit@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).