public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@wasabisystems.com>
To: cgen@sources.redhat.com
Subject: Re: Use of DI mode on 32-bit hosts
Date: Thu, 05 Jun 2003 13:34:00 -0000	[thread overview]
Message-ID: <87znkwve9z.fsf@sashimi.wasabisystems.com> (raw)
In-Reply-To: <20030605115059.GA16222@tiktok.the-meissners.org>

Michael Meissner <cgen-mail@the-meissners.org> writes:

> By the way, what is the way to configure cgen?  The toplevel
> makefile doesn't seem to go into the cgen directory, and if I
> configure cgen directly from the subdirectory, I get the following
> in the tmp-desc.h file:

I believe configuring from the top-level was removed because it was
thought that cgen didn't need configuring -- it runs entirely from the
source tree, via Makefile targets in other build directories, like
opcodes.

It was concluded that this is incorrect, though, because it is needed
to build the documentation at the very least.  I don't know if the
top-level gear was put back or not.

Ben

  reply	other threads:[~2003-06-05 13:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02 17:32 Michael Meissner
2003-06-02 17:45 ` Doug Evans
2003-06-02 19:22   ` Michael Meissner
2003-06-02 20:44     ` Doug Evans
2003-06-02 20:50       ` Frank Ch. Eigler
2003-06-02 21:26         ` Doug Evans
2003-06-02 21:32           ` Frank Ch. Eigler
2003-06-02 22:04             ` Doug Evans
2003-06-03 15:19               ` Frank Ch. Eigler
2003-06-02 21:33       ` Michael Meissner
2003-06-02 22:10         ` Doug Evans
2003-06-02 22:16           ` Doug Evans
2003-06-04 20:27         ` Doug Evans
2003-06-05 11:51           ` Michael Meissner
2003-06-05 13:34             ` Ben Elliston [this message]
2003-06-05 15:41               ` Doug Evans
2003-06-05 16:04             ` Doug Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87znkwve9z.fsf@sashimi.wasabisystems.com \
    --to=bje@wasabisystems.com \
    --cc=cgen@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).