From: Francisco Cuesta <ndarkness@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Cross-compilation shows>error: no termcap library found, why?
Date: Fri, 07 Jun 2013 14:30:00 -0000 [thread overview]
Message-ID: <CANMvdA8gMqUeQ6=1Ez870RzJ=o1uPHqPN1os49+h3E4bvTpH3Q@mail.gmail.com> (raw)
In-Reply-To: <51B1B3BC.7020105@redhat.com>
Hi Pedro,
I don't understand, I have the gdb server running in the target, this
is all arm archietecture. On the other hand I have my pc, which is x86
architecture, but for debugging in eclipse I have to point to the dbg
client (on the pc) which is going to connect to the dbg server on the
target. SO, both gdb client and gdbserver have to be compiled in arm,
that is correct or I missunderstand something?
Thanks in advance,
Ps: what's more, I have done what you suggested and if I did that on
top level directory of gdb I get the error related to termcap... I
guess in that directory is where I need to crosscompile the gdb
client, though.
2013/6/7 Pedro Alves <palves@redhat.com>:
> On 06/07/2013 10:52 AM, Francisco Cuesta wrote:
>> But now I have another doubt, if I want to crooscompile the gdb
>> "client" which is going to connect to the gdbserver, how can I do it?
>> Then, I will have to crosscompile the whole gdb suite right?
>
> Assuming gdb will run on your host non-ARM machine, no.
>
> Here's the chapter everyone building cross tools should read (do
> click the right arrow):
>
> http://www.sourceware.org/autobook/autobook/autobook_258.html
>
> And also, simplified from:
>
> http://www.flameeyes.eu/autotools-mythbuster/autoconf/canonical.html
>
> "
> When using autoconf, there are three system definitions (or machine definitions)
> that are used to identify the “actors” in the build process; (...) These three definitions are:
>
> host
>
> The system that is going to run the software once it is built. Once the software
> has been built, it will execute on this particular system.
>
> build
>
> The system where the build process is being executed. For most uses this
> would be the same as the host system, but in case of cross-compilation
> the two obviously differ.
>
> target
>
> The system against which the software being built will run on. This only exists, or rather
> has a meaning, when the software being built may interact specifically with a
> system that differs from the one it's being executed on (our host). This is the case
> for compilers, debuggers, profilers and analyzers and other tools in general.
> "
>
> So configure GDB with --target=arm-mv5sft-linux-gnueabi,
> and GDBserver with --host=arm-mv5sft-linux-gnueabi.
>
>>
>> regards!
>>
>> 2013/6/6 Pedro Alves <palves@redhat.com>:
>>> It sounds like you're running the top level's configure
>>> instead of gdbserver's. If you just want to build
>>> gdbserver, run the configure in gdb/gdbserver/.
>>>
>>> --
>>> Pedro Alves
>>>
>
>
> --
> Pedro Alves
next prev parent reply other threads:[~2013-06-07 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 15:03 Francisco Cuesta
2013-06-06 16:03 ` Pedro Alves
2013-06-07 6:00 ` Francisco Cuesta
2013-06-07 9:52 ` Francisco Cuesta
2013-06-07 10:20 ` Pedro Alves
2013-06-07 14:30 ` Francisco Cuesta [this message]
2013-06-11 9:03 ` Pedro Alves
2013-06-11 15:43 ` cross building gdb/gdbserver howto in the wiki (Re: Cross-compilation shows>error: no termcap library found, why?) 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='CANMvdA8gMqUeQ6=1Ez870RzJ=o1uPHqPN1os49+h3E4bvTpH3Q@mail.gmail.com' \
--to=ndarkness@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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