Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
	gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: (Patch) Attempt to get src-release working again
Date: Thu, 05 Dec 2002 15:01:00 -0000	[thread overview]
Message-ID: <m3el8wjcjb.fsf@gossamer.airs.com> (raw)
In-Reply-To: <3DEFD97E.6030405@redhat.com>

Andrew Cagney <ac131313@redhat.com> writes:

> > This is an attempt to get src-release working again. :-)
> > Committed as obvious.  I'm worried about the very complex tricks being
> > played with 'texinfo'; I've probably broken them, but since I can't figure
> > out what they were *supposed* to do, I can't figure out how to fix them.
> > 	* src-release: Configure host subdirs.
> 
> Broadly, where are the complex tricks involving texinfo?

I haven't looked closely at the new code.  However, I know that we
used to do some mildly funky stuff in order to ship
texinfo/texinfo.tex with a binutils release, while still supporting
building texinfo with all-texinfo, install-texinfo, etc., if the
complete texinfo sources were present in the source directory.

That was important for the Cygnus source tree and Cygnus releases--a
binutils release did not have the Texinfo sources, but a Cygnus tools
release did.  I doubt this is important for the binutils tree, which
as far as I know never has the texinfo sources anyhow.

Ian


      reply	other threads:[~2002-12-05 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 14:54 Nathanael Nerode
2002-12-05 15:00 ` Andrew Cagney
2002-12-05 15:01   ` Ian Lance Taylor [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=m3el8wjcjb.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=neroden@twcny.rr.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