From: Andrew Pinski <pinskia@physics.uc.edu>
To: Mark Mitchell <mark@codesourcery.com>, gdb@sources.redhat.com
Cc: binutils@sources.redhat.com, gcc-patches@gcc.gnu.org, dj@redhat.com
Subject: Re: PATCH: Fix fallout from at-file.texi in Makefile.in, texi2pod
Date: Tue, 11 Oct 2005 18:45:00 -0000 [thread overview]
Message-ID: <2e2ce61816de3525f270605d8582080a@physics.uc.edu> (raw)
In-Reply-To: <200510111836.j9BIak2k027668@sethra.codesourcery.com>
On Oct 11, 2005, at 2:36 PM, Mark Mitchell wrote:
>
> It turns out that older versions of makeinfo and texi2pod.pl both fail
> to support:
>
> @include @value{...}
Where does "@include @value" happen?
I don't see it anywhere in GCC's sources and I am able to build GCC
just fine with
makeinfo 4.6 without any troubles.
Also shouldn't this be CC'd to gdb since they also use the toplevel
makefile?
-- Pinski
next parent reply other threads:[~2005-10-11 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200510111836.j9BIak2k027668@sethra.codesourcery.com>
2005-10-11 18:45 ` Andrew Pinski [this message]
2005-10-11 18:49 ` Mark Mitchell
2005-10-11 18:57 ` Andrew Pinski
2005-10-11 19:03 ` Mark Mitchell
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=2e2ce61816de3525f270605d8582080a@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mark@codesourcery.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).