From: Anthony Green <green@redhat.com>
To: james_wang@sidynet.com
Cc: rhug-rhats@sources.redhat.com
Subject: rhug and auto* tools
Date: Tue, 01 Oct 2002 15:00:00 -0000 [thread overview]
Message-ID: <1033509626.1668.17.camel@dhcppc2> (raw)
Hi James,
For some reason I did not receive your email from Sep 24. I just came
across your note on the rhug-rhats web archive...
In any case, to answer your question, I am using automake 1.5, autoconf
2.52, and (this is the tricky one) a hacked version of libtool. I'll
put this up on the ftp site soon and let you know when that's been done.
In the meanwhile, you can simply copy the libtool bits from any of the
other rhug packages and use the standard automake/autoconf tools I
mentioned.
AG
next reply other threads:[~2002-10-01 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 15:00 Anthony Green [this message]
2002-11-02 8:25 T.J. Mather
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=1033509626.1668.17.camel@dhcppc2 \
--to=green@redhat.com \
--cc=james_wang@sidynet.com \
--cc=rhug-rhats@sources.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).