public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: tromey@redhat.com, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: MELT tutorial on the wiki
Date: Sat, 01 Aug 2009 07:06:00 -0000	[thread overview]
Message-ID: <20090801070602.GC25360@gmx.de> (raw)
In-Reply-To: <4A73DC50.5080604@starynkevitch.net>

* Basile STARYNKEVITCH wrote on Sat, Aug 01, 2009 at 08:10:24AM CEST:
> I don"t know really how to fix that quickly! I must confess that
> autoconf related files in GCC scares me a big lot. BTW, I really
> cannot imagine why GCC still required autoconf 2.59 specifically,
> and not 2.63. What is so specific about 2.59?

I will post patches to move to 2.64 and Automake 1.11; they are ready
(I only need to finish writing the emails) but I'm off-list for the
next week starting now.  :-)

Cheers,
Ralf

  reply	other threads:[~2009-08-01  7:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 15:52 Basile STARYNKEVITCH
2009-07-30 21:17 ` Tom Tromey
2009-07-31  6:27   ` Basile STARYNKEVITCH
2009-07-31 17:52     ` Tom Tromey
2009-07-31 20:16       ` Tom Tromey
2009-08-01  6:11         ` Basile STARYNKEVITCH
2009-08-01  7:06           ` Ralf Wildenhues [this message]
2009-08-02 14:57           ` Paolo Bonzini
2009-08-03 16:23           ` Tom Tromey
2009-08-03 19:21             ` Basile STARYNKEVITCH
2009-08-01  6:28       ` Dave Korn
2009-08-01  6:43         ` Basile STARYNKEVITCH
2009-08-01  6:58           ` Dave Korn
2009-08-03 16:12             ` Tom Tromey
2009-08-04 13:22               ` Dave Korn
2009-08-23 20:14         ` Ralf Wildenhues
2009-08-01  8:44   ` Paolo Bonzini
2009-08-01  8:57     ` Basile STARYNKEVITCH
2009-08-03 16:16     ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2009-05-10 12:02 Basile STARYNKEVITCH

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=20090801070602.GC25360@gmx.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=tromey@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).