Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Michael Snyder" <Michael.Snyder@palmsource.com>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: <gdb@sourceware.org>
Subject: RE: Error running remote gdb
Date: Fri, 08 Sep 2006 01:27:00 -0000	[thread overview]
Message-ID: <0F4DF2E21F33DD46BE7B8CDEEB0E16D307EA94@ussunex01.palmsource.com> (raw)
In-Reply-To: <F795765B112E7344AF36AA911279641502D19B97@xmb-sjc-212.amer.cisco.com>


> Here is how we build the gdb in our environment:
> First we edit the config.cache.emb file with the following statement:
> ac_cv_header_sys_reg_h=${ac_cv_header_sys_reg_h=no}
> ac_cv_lib_ncurses_tgetent=${ac_cv_lib_ncurses_tgetent=yes}
> srv_cv_thread_db=${srv_cv_thread_db="-lthread_db"}

Well, there is no file "config.cache.emb" in the public distro
nor in the fsf gdb repository, so who did you get that file from?

> Second we run the configure command as below:
> sh configure --prefix=/usr --cache-file=config.cache.emb
> --target=powerpc-linux-gnuspe --disable-sim

... and there is no target containing the string "gnuspe"
in any of our configure files.

>> By the way, what does "powerpc-linux-gnuspe"... mean?
> Our platform is based on MPC8541 powerpc processor from freescale.
> All of our toolchain have
> The "powerpc-linux-gnuspe" prefix for example the C compiler is:
> Powerpc-linux-gnuspe-gcc

Ah.  Well then, I assume these tools must have come from Freescale.

That's probably who you should be talking to.  This toolchain
is not in our version of gdb at all.


       reply	other threads:[~2006-09-08  1:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F795765B112E7344AF36AA911279641502D19B97@xmb-sjc-212.amer.cisco.com>
2006-09-08  1:27 ` Michael Snyder [this message]
2006-09-08  2:12   ` Daniel Jacobowitz
2006-09-08  2:01 Bizhan Gholikhamseh (bgholikh)
  -- strict thread matches above, loose matches on Subject: below --
2006-09-08  1:30 FW: " Bizhan Gholikhamseh (bgholikh)
2006-09-08  1:53 ` Michael Snyder
2006-09-06 11:47 Bizhan Gholikhamseh (bgholikh)
2006-09-07 22:48 ` Michael Snyder
2006-09-01  0:33 Bizhan Gholikhamseh (bgholikh)
2006-09-01  0:35 ` Daniel Jacobowitz
2006-09-01  3:31 ` Michael Snyder
2006-09-01  4:09   ` Daniel Jacobowitz
2006-09-02  0:05     ` Michael Snyder
2006-09-02  1:04       ` Daniel Jacobowitz
2006-08-31  0:39 Bizhan Gholikhamseh (bgholikh)
2006-08-31 22:47 ` Michael Snyder
2006-08-31 23:28   ` Daniel Jacobowitz
2006-09-01  3:13     ` Michael Snyder
2006-09-01  4:08       ` Daniel Jacobowitz
2006-08-30 22:37 Bizhan Gholikhamseh (bgholikh)
2006-08-30 23:11 ` Michael Snyder
2006-08-30 21:54 Bizhan Gholikhamseh (bgholikh)
2006-08-30 21:56 ` Daniel Jacobowitz
2006-08-30 23:08 ` Michael Snyder

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=0F4DF2E21F33DD46BE7B8CDEEB0E16D307EA94@ussunex01.palmsource.com \
    --to=michael.snyder@palmsource.com \
    --cc=bgholikh@cisco.com \
    --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