public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: binutils@sources.redhat.com,  gcc-patches@gcc.gnu.org,
	 dj@redhat.com,  gdb@sources.redhat.com
Subject: Re: PATCH: Fix fallout from at-file.texi in Makefile.in, texi2pod
Date: Tue, 11 Oct 2005 19:03:00 -0000	[thread overview]
Message-ID: <434C0C87.9010005@codesourcery.com> (raw)
In-Reply-To: <67184be4e18626ff4f251b86f300a522@physics.uc.edu>

Andrew Pinski wrote:
> 
> On Oct 11, 2005, at 2:49 PM, Mark Mitchell wrote:
> 
>> Andrew Pinski wrote:
>>
>>> Where does "@include @value" happen?
>>
>>
>> Binutils.  And, presumably, all future uses of expandargv from libiberty.
>  
> 4.8 was only released this January which seems too early to require this
> new version and even too late into the release cycle of GCC.

I disagree.  Building GCC requires lots of tools; there's no reason to
tie our hands by requiring tools that are more than a year old.

However, since I realized that I have makeinfo 4.5, I tried that; it
seems to work OK too.  So, consider the patch amended to use makeinfo
4.5.  (That version is installed as/usr/bin/makeinfo on RHEL 3, so it's
not terribly recent.)

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304

      reply	other threads:[~2005-10-11 19:03 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
2005-10-11 18:49   ` Mark Mitchell
2005-10-11 18:57     ` Andrew Pinski
2005-10-11 19:03       ` Mark Mitchell [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=434C0C87.9010005@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=pinskia@physics.uc.edu \
    /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).