From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Wilzon L" To: insight@sourceware.cygnus.com Subject: Again: No GUI with ARM AEB-1 Date: Fri, 03 Mar 2000 02:23:00 -0000 Message-id: <20000303102249.30528.qmail@hotmail.com> X-SW-Source: 2000-q1/msg00113.html Hello, I wrote yesterday about my problem getting insight GUI based gdb to work with ARM-EvBoard AEB-1. Background: OS: Red-Hat-Linux 6.1 (Full install) First I downloaded ecos (ecosSWtools-arm-990321-src.tar.gz)and extracted and built it successfully. Finally I extracted the ecos-1.2.1.tar.gz. I downloaded the GDB-stub onto the AEB-1 and installed it on the FLASH. Now if I use $arm-elf-gdb -nw hello (hello.c is in the examples dir of eCos) everything works fine, but from now on I would like to activate the Insight-GUI for GDB. Ok, so I downloaded insight-20000204.tar.bz2 and from /tmp/insight-20000204 I invoked ./configure and then 'make install' which put some binaries into /usr/local/bin Here I must say I'm a little bit confused because on my system there must be 3 different GDB:s. Namely: 1. arm-elf-gdb 2. gdb (v4.18) (native?) 3. gdb (insight with GUI) Using $/usr/local/bin/gdb with binaries built with arm-elf-gcc gives some output about not compatible with i686-pc-linux-gnu. The 'Getting Started With eCos' chap 13 has a small note about the '-nw' option saying that without it insight-GUI would be invoked. Well it doesn't. How could it? The insight-20000204.tar.bz2 hasn't been built for ARM AEB-1. So finally my question is: How do I make the Insight-gdb work with 'ARM AEB-1' ? Thanks everyone who takes interest in this matter. Sincerely Wilzon. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com