Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Klee Dienes <klee@apple.com>,
	binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
Date: Thu, 05 Dec 2002 13:16:00 -0000	[thread overview]
Message-ID: <20021205211657.GA19698@nevyn.them.org> (raw)
In-Reply-To: <3DEFC16A.50807@redhat.com>

On Thu, Dec 05, 2002 at 04:13:14PM -0500, Andrew Cagney wrote:
> 
> >>I'm not sure I understand the question, but I'll elaborate on the 
> >>situation a bit in hopes that I can answer it anyway.
> >>
> >>Automake-1.4p5 generates Makefile.in's that use the syntax:
> >>
> >>ylwrap PROGRAM INPUT [OUTPUT DESIRED]... -- [ARGS]...
> >>
> >>Automake-1.7 generates Makefile.in's that use the syntax:
> >>
> >>ylwrap INPUT [OUTPUT DESIRED]... -- PROGRAM [ARGS]...
> >>
> >>So if we use automake-1.7 to build Makefile.in binutils/ld/gas, we need 
> >>to use the ylwrap from automake-1.7 as well, which uses the new syntax 
> >>and therefore requires the change to the GDB Makefile.in.   I don't 
> >>think it's possible to have a version of the GDB Makefile.in that works 
> >>with both versions.
> >
> >
> >But, to clarify even further: if we use the new ylwrap from Automake
> >1.7, regardless of what version of _automake_ we are using, then Klee's
> >patch to gdb/Makefile.in will work.
> >
> >This means that all directories which use both automake and ylwrap must
> >be converted at the same time however.
> 
> [australian expletive deleted]
> 
> But GDB, which doesn't use automake, can start using the new one 
> (locally) now, and get the patches committed?

Probably not.  It expects it to be in the toplevel directory.  Might be
able to override YLWRAP for now.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-12-05 21:16 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13  8:55 [RFA/PATCH] Darwin fixes for ltconfig, ltcf-c.sh Klee Dienes
2002-11-13  9:57 ` Andrew Cagney
2002-11-13 10:32   ` Klee Dienes
2002-12-04 22:04     ` [RFC] Update to current automake/autoconf/libtool versions Klee Dienes
2002-12-05  5:26       ` Hans-Peter Nilsson
2002-12-05 14:07         ` Alan Modra
2002-12-05  7:43       ` Andrew Cagney
2002-12-05  8:22         ` Klee Dienes
2002-12-05  9:01           ` Andrew Cagney
2002-12-05 12:55             ` Klee Dienes
2002-12-05 13:03               ` Daniel Jacobowitz
2002-12-05 13:13                 ` Andrew Cagney
2002-12-05 13:16                   ` Daniel Jacobowitz [this message]
2002-12-05 13:08               ` Andrew Cagney
2002-12-05 13:18                 ` Klee Dienes
2002-12-05  8:28         ` DJ Delorie
2002-12-05  9:37           ` Klee Dienes
2002-12-05  9:42             ` DJ Delorie
2002-12-05 10:28               ` Klee Dienes
2002-12-05  9:31         ` H. J. Lu
2002-12-05  7:44       ` Maciej W. Rozycki
2002-12-05  9:01         ` Klee Dienes
2002-12-05  8:09       ` Daniel Jacobowitz
2002-12-05  8:29         ` DJ Delorie
2002-12-05  8:35           ` Daniel Jacobowitz
2002-12-05  8:37             ` DJ Delorie
2002-12-05  8:40             ` Maciej W. Rozycki
2002-12-05  8:44               ` Daniel Jacobowitz
2002-12-05  9:19                 ` Elena Zannoni
2002-12-05  9:54                 ` Klee Dienes
2002-12-05 10:10                   ` Maciej W. Rozycki
2002-12-05 10:59                   ` Doug Evans
2002-12-05 12:11                     ` Klee Dienes
2002-12-05 12:23                       ` Ian Lance Taylor
2002-12-05 14:29                         ` Klee Dienes
2002-12-06  5:34                     ` Maciej W. Rozycki
2002-12-06  7:25                       ` DJ Delorie
2002-12-06  8:06                         ` Maciej W. Rozycki
2002-12-06  8:47                           ` DJ Delorie
2002-12-05 10:59                   ` Andrew Cagney
2002-12-06  5:52                     ` Maciej W. Rozycki
2002-12-05 13:59                   ` Ben Elliston
2002-12-05 13:41                     ` Ben Elliston
2002-12-30 16:10       ` Alexandre Oliva
2002-12-05 10:15 Michael Elizabeth Chastain
2002-12-05 10:37 ` Klee Dienes
2002-12-05 11:08 Nathanael Nerode
2002-12-05 11:31 ` Andrew Cagney
2002-12-05 13:31 ` Zack Weinberg
2002-12-05 14:36   ` Alan Modra
2002-12-05 14:56     ` Ian Lance Taylor
2002-12-05 15:22       ` Alan Modra
2002-12-05 15:43         ` Ian Lance Taylor
2002-12-05 15:51           ` Andrew Cagney
2002-12-05 15:47         ` Mike Stump
2002-12-05 16:30           ` Alan Modra
2002-12-05 16:45             ` Zack Weinberg
2002-12-08  2:49         ` Klee Dienes
2002-12-05 14:29 ` Christopher Faylor
2002-12-06  6:45 ` Maciej W. Rozycki
2002-12-08 10:53 ` Klee Dienes
2002-12-05 14:40 Nathanael Nerode
2002-12-05 15:19 ` Zack Weinberg
2002-12-06 10:21   ` Tom Tromey
2002-12-07 13:06   ` Alexandre Oliva
2002-12-07 16:03     ` Zack Weinberg
2002-12-09 19:16       ` Alexandre Oliva
2002-12-09 21:52         ` Geoff Keating
2002-12-08 13:11     ` Tom Tromey
2002-12-05 14:42 Joern Rennecke
2002-12-06  5:28 Nathanael Nerode
     [not found] <9A4230D6-1D26-11D7-BFCA-00039396EEB8@apple.com>
2003-01-12 13:22 ` Alexandre Oliva

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=20021205211657.GA19698@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=klee@apple.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