unable to compile gdb 6.0 as a cross gdb

Wolcott, Ken (MED, Compuware) Ken.Wolcott@med.ge.com
Tue Oct 28 14:49:00 GMT 2003


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: kaw_make.log.gz
Type: application/x-gzip
Size: 16311 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20031028/ce07e360/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compile.sh
Type: application/x-shellscript
Size: 1181 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20031028/ce07e360/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.status
Type: application/x-shellscript
Size: 8799 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20031028/ce07e360/attachment-0002.bin>
-------------- next part --------------
------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


More information about the crossgcc mailing list