From: Ben Elliston <bje@redhat.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: cgen@sources.redhat.com
Subject: Re: [RFA:] Improve cgen/doc/rtl.texi wrt. timing and PROFILE.
Date: Sat, 30 Nov 2002 03:18:00 -0000 [thread overview]
Message-ID: <m3znrrqpaw.fsf@scooby.brisbane.redhat.com> (raw)
In-Reply-To: Hans-Peter Nilsson's message of "Sat, 30 Nov 2002 09:24:57 +0100"
>>>>> "Hans-Peter" == Hans-Peter Nilsson <hans-peter.nilsson@axis.com> writes:
Hans-Peter> Slight improvements to the documentation, I hope. By
Hans-Peter> the way, it seems toplevel configury does not create a
Hans-Peter> cgen/Makefile, necessary for "make info" to take effect,
Hans-Peter> even though nothing else is created object-wise. Needs
Hans-Peter> fixing.
Ah yes -- this is indeed a problem.
The easiest way to solve it for now is to re-introduce cgen in the
host_tools list and have the top-level configure script configure the
src/cgen directory. Then "make info" and "make install-info" will
work. Feel free to initiate such a patch!
Cheers, Ben
prev parent reply other threads:[~2002-11-30 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-30 0:25 Hans-Peter Nilsson
2002-11-30 3:18 ` Ben Elliston
2002-11-30 3:18 ` 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=m3znrrqpaw.fsf@scooby.brisbane.redhat.com \
--to=bje@redhat.com \
--cc=cgen@sources.redhat.com \
--cc=hans-peter.nilsson@axis.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).