This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

unable to compile gdb 6.0 as a cross gdb; error: cannot run test program while cross compiling (compressed attachment now)



----------  Forwarded Message  ----------

Subject: unable to compile gdb 6.0 as a cross gdb; error: cannot run test 
program while cross compiling
Date: Mon, 27 Oct 2003 17:47:52 -0600
From: "Wolcott, Ken (MED, Compuware)" <Ken.Wolcott@med.ge.com>
To: crossgcc@sources.redhat.com, gdb mailing list <gdb@sources.redhat.com>,   
gcc mailing list <gcc@sources.redhat.com>

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: compile.sh
Description: application/shellscript

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:581: checking host system type
configure:602: checking target system type
configure:620: checking build system type
configure:2697: checking for arm-arm9-linux-gnu-ar
configure:2769: checking for arm-arm9-linux-gnu-as
configure:2841: checking for arm-arm9-linux-gnu-dlltool
configure:2913: checking for arm-arm9-linux-gnu-ld
configure:2985: checking for arm-arm9-linux-gnu-nm
configure:3057: checking for arm-arm9-linux-gnu-ranlib
configure:3129: checking for arm-arm9-linux-gnu-windres
configure:3201: checking for arm-arm9-linux-gnu-objcopy
configure:3273: checking for arm-arm9-linux-gnu-objdump
configure:3354: checking for arm-arm9-linux-gnu-ar
configure:3426: checking for arm-arm9-linux-gnu-as
configure:3498: checking for arm-arm9-linux-gnu-dlltool
configure:3570: checking for arm-arm9-linux-gnu-ld
configure:3642: checking for arm-arm9-linux-gnu-nm
configure:3714: checking for arm-arm9-linux-gnu-ranlib
configure:3786: checking for arm-arm9-linux-gnu-windres
configure:3886: checking whether to enable maintainer-specific portions of Makefiles

Attachment: kaw_make.log.gz
Description: GNU Zip compressed data

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]