From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32579 invoked by alias); 15 Jun 2003 16:55:46 -0000 Mailing-List: contact cgen-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cgen-owner@sources.redhat.com Received: (qmail 32448 invoked from network); 15 Jun 2003 16:55:43 -0000 Received: from unknown (HELO tiktok.the-meissners.org) (130.105.39.7) by sources.redhat.com with SMTP; 15 Jun 2003 16:55:43 -0000 Received: from tiktok.the-meissners.org (localhost [127.0.0.1]) by tiktok.the-meissners.org (8.12.8/8.12.8) with ESMTP id h5FGtfZT006511 for ; Sun, 15 Jun 2003 12:55:41 -0400 Received: (from meissner@localhost) by tiktok.the-meissners.org (8.12.8/8.12.8/Submit) id h5FGtfom006509 for cgen@sources.redhat.com; Sun, 15 Jun 2003 12:55:41 -0400 Date: Sun, 15 Jun 2003 16:55:00 -0000 From: Michael Meissner To: cgen@sources.redhat.com Subject: Re: Exact sequences for running cgen Message-ID: <20030615165541.GA6502@tiktok.the-meissners.org> Mail-Followup-To: Michael Meissner , cgen@sources.redhat.com References: <20030613170851.GA31204@tiktok.the-meissners.org> <16106.5336.275159.592263@casey.transmeta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16106.5336.275159.592263@casey.transmeta.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2003-q2/txt/msg00113.txt.bz2 On Fri, Jun 13, 2003 at 11:15:52AM -0700, Doug Evans wrote: > Michael Meissner writes: > > Ok, I must be doing something wrong. Could somebody give me an exact > > walk-through of how to set up the cgen environment. I have tried using the cvs > > sources, and the snapshot. I have tried building cgen in place, as well as my > > usual preference of building it in a separate build directory. The last time I > > asked this question, I was told just run the make in place, but neither the > > snapshot nor the cvs sources have a Makefile. I have tried using a Red Hat 8.0 > > system, as well as Red Hat 9 (using a 1.4.3 guile compiled since > > > > Here is one attempt: > > > > $ tar -xvjf snapshot-20030607.tar.bz2 > > $ cd cgen/cgen > > $ ./configure --target=m32r-unknown-elf > > $ make desc > > > > At this point it runs, but if you look at the tmp-desc.h and tmp-desc.c files, > > you see that it has not substituted M32R for @ARCH@ and m32r for @arch@ as I > > would expect. See the attachments for the tmp-desc.h and tmp-desc.c files. > > The tmp-desc.[ch] files get subsequently fed through sed to s/@ARCH@/FOO/ > and this happens when you run the generators from the opcodes directory. > "Final" versions of the generated files are always built from the > application dir (pedantic: except html since there is no app. dir). > The rules in cgen/Makefile exist just so one can generate something > and have a gander at them to see if they look correct. > > In normal production work, one configures with --enable-cgen-maint, > and builds in the opcodes directory and lets the dependencies > in opcodes/Makefile regenerate the files whenever the .cpu file changes. > Ditto for sim, sid, etc. > > So, exact walk-through: > > 1) mkdir obj > 2) cd obj > 3) /path/to/binutils+cgen/configure --target=m32r-elf --enable-cgen-maint > 4) touch /path/to/binutils+cgen/cgen/cpu/m32r.cpu # ensure files get rebuilt > 5) cd opcodes > 6) make stamp-m32r Thanks, thats a help. I guess I missed it on the first read-through of the manual. -- Michael Meissner email: gnu@the-meissners.org http://www.the-meissners.org