Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Stefano Lattarini <stefano.lattarini@gmail.com>
Cc: 11034@debbugs.gnu.org, binutils@sourceware.org,
	gdb@sourceware.org,     gcc@gcc.gnu.org,
	Automake List <automake@gnu.org>
Subject: Re: Binutils, GDB, GCC and Automake's 'cygnus' option
Date: Wed, 28 Mar 2012 12:29:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1203281223390.13451@digraph.polyomino.org.uk> (raw)
In-Reply-To: <4F7301DD.7090401@gmail.com>

On Wed, 28 Mar 2012, Stefano Lattarini wrote:

>   - texinfo.tex is not required if a Texinfo source file is specified. The
>     assumption is that the file will be supplied, but in a place that
>     Automake cannot find. This assumption is an artifact of how Cygnus
>     packages are typically bundled.

texinfo.tex is in a known location, but only a single copy for GDB and 
binutils and a single copy for GCC rather than in each directory needing 
it.  Is the approach used (for example) in libquadmath/Makefile.am

TEXINFO_TEX   = ../gcc/doc/include/texinfo.tex

considered a suitable approach for this case?

>   - Certain tools will be searched for in the build tree as well as in the
>     user's PATH. These tools are runtest, expect, makeinfo and texi2dvi.

I did previously suggest removing the existing support for building and 
using these tools in-tree 
<http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01674.html>, but there was 
pushback on that.  I don't know, however, if it actually depends on 
anything built into automake.

>   - The check target doesn't depend on all.

I'm not aware of a need for that.

-- 
Joseph S. Myers
joseph@codesourcery.com


  reply	other threads:[~2012-03-28 12:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 10:05 Stefano Lattarini
2012-03-28 11:25 ` Joseph S. Myers
2012-03-28 12:20   ` Stefano Lattarini
2012-03-28 12:29     ` Joseph S. Myers [this message]
2012-03-28 13:02       ` Stefano Lattarini
2012-03-28 23:43     ` Ian Lance Taylor
2012-03-31  8:30       ` bug#11034: " Stefano Lattarini
2012-03-31  9:08         ` Alfred M. Szmidt
2012-03-31 10:14           ` Stefano Lattarini
2012-04-04 13:18             ` Joseph S. Myers
2012-04-05 12:04               ` Stefano Lattarini
     [not found]           ` <4F76D8F2.8050804__46768.5595191599$1333188914$gmane$org@gmail.com>
2012-04-02 14:26             ` Tom Tromey
2012-04-02 15:04               ` Stefano Lattarini
2012-04-02 15:17                 ` Tom Tromey
2012-04-02 15:30                   ` Stefano Lattarini
     [not found]                   ` <4F79C5F2.2020807__46832.8654104427$1333380662$gmane$org@gmail.com>
2012-04-02 19:37                     ` Tom Tromey
2012-04-02 19:51                       ` Stefano Lattarini
     [not found]                       ` <4F7A0341.9050305__49963.8538728051$1333396325$gmane$org@gmail.com>
2012-04-02 20:19                         ` Tom Tromey
2012-04-02 20:50                           ` Stefano Lattarini
2012-04-02 21:10                             ` Ian Lance Taylor
2012-04-03 20:04                               ` Stefano Lattarini
2012-04-03 20:05                                 ` Stefano Lattarini
2012-04-03 20:29                                   ` Stefano Lattarini
2012-04-03 20:40                                     ` Tom Tromey
2012-04-04  7:43                                       ` Stefano Lattarini
2012-04-03 21:08                                 ` Ian Lance Taylor
2012-04-03 21:40                                 ` Pedro Alves
2012-04-03 23:53                                   ` Miles Bader
2012-04-04  7:47                                     ` Stefano Lattarini
2012-04-04  9:03                                     ` Pedro Alves
2012-04-03  8:23                             ` Joern Rennecke
2012-03-31 11:39     ` Stefano Lattarini
2012-03-31 16:42       ` bug#11034: " Stefano Lattarini

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=Pine.LNX.4.64.1203281223390.13451@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=11034@debbugs.gnu.org \
    --cc=automake@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=stefano.lattarini@gmail.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