From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4832 invoked by alias); 21 Mar 2002 02:42:34 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 4689 invoked from network); 21 Mar 2002 02:42:31 -0000 Received: from unknown (HELO hypatia.brisbane.redhat.com) (202.83.74.3) by sources.redhat.com with SMTP; 21 Mar 2002 02:42:31 -0000 Received: from localhost (bje@localhost) by hypatia.brisbane.redhat.com (8.11.6/8.11.6) with ESMTP id g2L2g1808721; Thu, 21 Mar 2002 12:42:01 +1000 Date: Wed, 20 Mar 2002 18:42:00 -0000 From: Ben Elliston X-X-Sender: bje@hypatia.brisbane.redhat.com To: Robert Lee cc: sid@sources.redhat.com Subject: Re: how to get started? In-Reply-To: <20020321020258.42494.qmail@web9010.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-q1/txt/msg00044.txt.bz2 Hi. > I heard about SID and I think it is cool. Thanks! (And thanks for your interest). > I checked out the source code, did "make" and "make > install". Everything looked fine. I got a directory > which contains bin/, include/, info/, lib/, man/, and > share/. In bin/, I found files such as sid and > configrun-sid. Then, I am lost. configrun-sid is not run directly (although it can be). There are two ways to run sid: sid (as you have done with i386-gdb.conf). or via a front-end script which generates a customised configuration file based on the options you pass to the script on the command line. For example, see arm-elf-sid --help. > Finally, I tried "sid i386-gdb.conf" and it seemed hanging. It's not hanging; it is blocked waiting for a connection from GDB. Cheers, Ben