public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Orlando Arias <oarias@knights.ucf.edu>
To: <gdb@sourceware.org>
Subject: Re: gdbserver - manually modify Makefile
Date: Thu, 13 Aug 2015 20:53:00 -0000	[thread overview]
Message-ID: <55CD03CE.3080906@knights.ucf.edu> (raw)
In-Reply-To: <CAJ2oMh+5j+Rk7s0uH=Og7jaDmtrAQp2UDCdaM4rMhQe3L5Dt5A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

Greetings,

I believe this is happening because you need to supply a --target
parameter to gdbserver as well.

./configure --host=powerpc-buildroot-linux-gnu \
	--target=powerpc-buildroot-linux-gnu \
	--disable-werror

Cheers,
Orlando.

On 08/13/2015 04: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
> 
> 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.
> 
> Can anyone help me understand what was wrong doing in the above steps?
> 
> Since this didn't work as expected I'm afraid that maybe the gdb as I
> compiled might also required some manually modifications which I am
> not aware of.
> These are the steps for gdb build:
> ubuntu@ubuntu-laptop:~/gdb-7.9.1/$ sudo ./configure
> --target=powerpc-buildroot-linux-gnu --disable-werror
> 
> Thank you for your assistance,
> Ran
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-13 20:53 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 [this message]
2015-08-13 21:58 ` Pedro Alves
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=55CD03CE.3080906@knights.ucf.edu \
    --to=oarias@knights.ucf.edu \
    --cc=gdb@sourceware.org \
    /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).