From: Ben Elliston <bje@redhat.com>
To: Johan Rydberg <jrydberg@rtmk.org>
Cc: cgen@sources.redhat.com
Subject: Re: Calling C functions
Date: Tue, 12 Mar 2002 18:41:00 -0000 [thread overview]
Message-ID: <15502.48212.58723.19304@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <20020313030919.E8492@localhost>
>>>>> "Johan" == Johan Rydberg <jrydberg@rtmk.org> writes:
Johan> It can not be that easy that Jose just forgot to configure with
Johan> --enable-cgen-maint ? From memory, I think that must be enabled to
Johan> enable the regenerate rules in opcodes/Makefile.[am|in|]
The rules are still present in the opcodes Makefile; they just aren't
a dependency rule for `make all' which is what --enable-cgen-maint
does.
Ben
prev parent reply other threads:[~2002-03-13 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:53 Jose Luis Ayala
2002-03-12 2:01 ` Frank Ch. Eigler
2002-03-12 2:02 ` Ben Elliston
2002-03-12 17:58 ` Johan Rydberg
2002-03-12 18:41 ` Ben Elliston [this message]
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=15502.48212.58723.19304@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=jrydberg@rtmk.org \
/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).