public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Sachin Rao" <Sachin@sinett.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sources.redhat.com>
Subject: RE: Help with compiling GDB for PPC
Date: Tue, 21 Feb 2006 06:55:00 -0000	[thread overview]
Message-ID: <BB6D74C75CC76A419B6D6FA7C38317B2E804CD@sinett-sbs.SiNett.LAN> (raw)

Thanks, & do I need to change the include path in the Makefile to point
to the native PPC Linux include path? I could not find the reference to
the path anywhere in the generated Makefile...

--

Sachin.

-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Monday, February 20, 2006 7:18 PM
To: Sachin Rao
Cc: gdb@sources.redhat.com
Subject: Re: Help with compiling GDB for PPC

On Sun, Feb 19, 2006 at 09:53:41PM -0800, Sachin Rao wrote:
> Hi,
> 
> We have a rather old version of GDB (5.2.1) cross-compiled for the PPC
> target. I wish to use the latest GDB source to compile a newer version
> of GDB using the native PPC compiler toolchain that we have. For this
I
> tried 
> 
> ./configure --target=powerpc-hardhat-linux
--host=powerpc-hardhat-linux
> 
>  And then modified the CC, LD, AS, AR defines in the Makefile to point
> to the respective native PPC compiler tools, but the build failed,
first
> in the readline module. 
> 
> I wanted to know if iam going about it the right way, or is there a
> better way to accomplish this task?

You need to set one autoconf variable for readline in order for this to
work, I think it's bash_cv_have_mbstate_t=yes.

-- 
Daniel Jacobowitz
CodeSourcery


             reply	other threads:[~2006-02-21  4:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21  6:55 Sachin Rao [this message]
2006-02-21 18:12 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-02-20  7:26 Sachin Rao
2006-02-20 18:57 ` Daniel Jacobowitz

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=BB6D74C75CC76A419B6D6FA7C38317B2E804CD@sinett-sbs.SiNett.LAN \
    --to=sachin@sinett.com \
    --cc=drow@false.org \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).