From: "Anthony Green" <green@redhat.com>
To: <tromey@redhat.com>, <apbianco@cygnus.com>
Cc: <rhug-rhats@sources.redhat.com>
Subject: Re: Patch: BouncyCastle
Date: Wed, 17 Oct 2001 12:22:00 -0000 [thread overview]
Message-ID: <013101c15741$c5511280$5be6b4cd@cygnus.com> (raw)
In-Reply-To: <87669ekrvy.fsf@creche.redhat.com>
Tom wrote:
> rhug/configure.in doesn't have any code to process --enable-bouncycastle.
> I don't think it is required right now. I ended up having to generate
> the Makefile myself like this:
>
> CONFIG_FILES=BouncyCastle/Makefile ./config.status
Whoops. I forgot to check it in.
In any case, it seems like it would be better to automatically configure the
BoucyCastle stuff if the upstream src directory exists. Is this easy to do?
AG
next prev parent reply other threads:[~2001-10-17 12:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 9:47 Tom Tromey
2001-10-17 10:01 ` Alexandre Petit-Bianco
2001-10-17 11:50 ` Tom Tromey
2001-10-17 12:22 ` Anthony Green [this message]
2001-10-17 12:26 ` Alexandre Petit-Bianco
2001-10-17 12:29 ` Anthony Green
2001-10-17 12:30 ` Tom Tromey
2001-10-17 21:03 ` Anthony Green
2001-10-18 9:22 ` Tom Tromey
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='013101c15741$c5511280$5be6b4cd@cygnus.com' \
--to=green@redhat.com \
--cc=apbianco@cygnus.com \
--cc=rhug-rhats@sources.redhat.com \
--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).