public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: fche@redhat.com
Cc: cgen@sourceware.org
Subject: Re: Using newer autoconf in src/cgen directory
Date: Fri, 05 May 2006 17:18:00 -0000	[thread overview]
Message-ID: <200605051718.KAA02843@hpsje.cup.hp.com> (raw)
In-Reply-To: <20060505001617.GB8699@redhat.com>

> > I have been working to move the src tree at soureware.org to a newer
> > version of autoconf.  The reason for this is so that we can, in turn,
> > move to a newer version of libtool.  Would it be possible to rebuild the
> > configure script in src/cgen with autoconf 2.59?  [...]
> 
> Feel free to commit those changes.  cgen is barely worthy of autoconf
> anyway, being an interpreted program and all.
> 
> - FChE

OK, Here is what I commited.  Let me know if there are any problems.

Steve Ellcey
sje@cup.hp.com


2006-05-05  Steve Ellcey  <sje@cup.hp.com>

        * configure.in: Remove AC_ARG_PROGRAM.
        * configure: Regenerate with autoconf 2.59.


Index: configure.in
===================================================================
RCS file: /cvs/src/src/cgen/configure.in,v
retrieving revision 1.1.1.1
diff -c -3 -p -r1.1.1.1 configure.in
*** configure.in        28 Jul 2000 04:11:52 -0000      1.1.1.1
--- configure.in        5 May 2006 17:06:00 -0000
*************** arch=${target_cpu}
*** 13,18 ****
  AC_SUBST(arch)

  AM_MAINTAINER_MODE
- AC_ARG_PROGRAM

  AC_OUTPUT([Makefile doc/Makefile])
--- 13,17 ----

      parent reply	other threads:[~2006-05-05 17:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 20:34 Steve Ellcey
2006-05-05  0:18 ` Frank Ch. Eigler
2006-05-05  0:31   ` Doug Evans
2006-05-05  0:35     ` Frank Ch. Eigler
2006-05-05  0:45       ` Doug Evans
2006-05-05 17:18   ` Steve Ellcey [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=200605051718.KAA02843@hpsje.cup.hp.com \
    --to=sje@cup.hp.com \
    --cc=cgen@sourceware.org \
    --cc=fche@redhat.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).