From: "Wolcott, Ken (MED, Compuware)" <Ken.Wolcott@med.ge.com>
To: gleb@nbase.co.il
Cc: crossgcc@sources.redhat.com,
gdb mailing list <gdb@sources.redhat.com>,
gcc mailing list <gcc@sources.redhat.com>
Subject: Re: unable to compile gdb 6.0 as a cross gdb
Date: Tue, 28 Oct 2003 14:49:00 -0000 [thread overview]
Message-ID: <200310280850.57972.ken.wolcott@med.ge.com> (raw)
In-Reply-To: <20031028063209.GN2280@nbase.co.il>
[-- Attachment #1: Type: text/plain, Size: 1957 bytes --]
HI Gleb;
Doing this (export bash_cv_have_mbstate_t=yes) solved the current problem
regarding the cross gdb build failure, however, I still end up with a gdb
which appears to be an Intel executeable.
file gdb
gdb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically
linked (uses shared libs), not stripped
I notice in the output (compressed, attached) that the gcc is being called,
not arm-arm9-linux-gnu-gcc. To me that implies that --with-gcc=/path/to/gcc
configure option is not working.
Thanks,
Ken
On Tuesday 28 October 2003 00:32, Gleb Natapov wrote:
> Hello,
>
> Try to do "export bash_cv_have_mbstate_t=yes" before running configure.
>
> On Mon, Oct 27, 2003 at 05:47:52PM -0600, Wolcott, Ken (MED, Compuware)
wrote:
> > Hi;
> >
> > I used Dan Kegel's crosstool version 0.24
> > (http://www.kegel.com/crosstool/) to create an arm9 cross tool chain.
> > I'm now trying to create an arm9 native gdb.
> >
> > One of the developers I'm trying to support says that he gets the error
> > msg"GDB can't read core files on this machine". So he wants an arm9
> > native gdb rather than aarm9 crossgdb.
> >
> > I have downloaded the gdb 6.0 source, expanded it, created a sibling
> > directory for my gdb build, executed configure and make using the
> > attached compile.sh script from the gdb build directory I created. The
> > captured output is also attached as kaw_make.log. There is mention of
> > config.log, so I attached it as well.
> >
> > All I need is a gdb that can read an arm9 corefile. Whether that is a
> > cross gdb (host: i686-pc-linux, target: arm-arm9-linux) or an arm9 native
> > gdb, it doesn't matter.
> >
> > Thanks,
> > Ken
--
Kenneth A. Wolcott
Consultant, Clinical Systems Engineering
GE Medical Systems Information Technologies
8200 West Tower Avenue, Milwaukee, WI 53223
Phone: 414/362-2720
Email: Ken.Wolcott@med.ge.com
[-- Attachment #2: kaw_make.log.gz --]
[-- Type: application/x-gzip, Size: 16311 bytes --]
[-- Attachment #3: compile.sh --]
[-- Type: application/x-shellscript, Size: 1181 bytes --]
[-- Attachment #4: config.status --]
[-- Type: application/x-shellscript, Size: 8798 bytes --]
next prev parent reply other threads:[~2003-10-28 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310271747.52297.ken.wolcott@med.ge.com>
2003-10-28 6:32 ` unable to compile gdb 6.0 as a cross gdb; error: cannot run test program while cross compiling Gleb Natapov
2003-10-28 14:49 ` Wolcott, Ken (MED, Compuware) [this message]
[not found] ` <200310281147.46663.ken.wolcott@med.ge.com>
[not found] ` <20031028175402.GA30757@timberwolf.dyndns.org>
2003-10-28 19:18 ` unable to compile gdb 6.0 as a cross gdb; no termcap library found; and plain gcc is still called Wolcott, Ken (MED, Compuware)
2003-10-28 19:48 ` Dan Kegel
2003-10-28 21:28 ` Wolcott, Ken (MED, Compuware)
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=200310280850.57972.ken.wolcott@med.ge.com \
--to=ken.wolcott@med.ge.com \
--cc=crossgcc@sources.redhat.com \
--cc=gcc@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=gleb@nbase.co.il \
/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