public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Petit-Bianco <apbianco@cygnus.com>
To: <rhug-rhats@sources.redhat.com>
Subject: Re: bouncycastle JCE
Date: Fri, 05 Oct 2001 21:21:00 -0000	[thread overview]
Message-ID: <15294.34486.581237.51727@fencer.cygnus.com> (raw)
In-Reply-To: <000201c14448$5d56fac0$0300a8c0@green>

Anthony Green writes:

> Also, Alex, if you look at the Makefile - I've special cased two
> "gcj -C" builds because the compiler goes into a seemingly endless
> loop.

I filed a PR for that (java/4489) and there's a simple workaround.

./A

2001-10-05  Alexandre Petit-Bianco  <apbianco@redhat.com>

	* Makefile.am: Removed workaround java/4489.
	* Makefile.in: Regenerate.
	* upstream/src/org/bouncycastle/crypto/engines/RijndaelEngine.java
	(generateWorkingKey): Installed workaround java/4489.

Index: Makefile.am
===================================================================
RCS file: /cvs/rhug/rhug/BouncyCastle/Makefile.am,v
retrieving revision 1.1
diff -u -p -r1.1 Makefile.am
--- Makefile.am 2001/09/23 00:12:18     1.1
+++ Makefile.am 2001/10/06 04:17:41
@@ -420,10 +420,10 @@ SUFFIXES = .java .lo .o .obj .class .jar
 
 # "gcj -C" current goes into a seemingly never ending loop.  Here's a
 # work-around.
-upstream/src/org/bouncycastle/crypto/engines/RijndaelEngine.class: upstream/src/org/bouncycastle/crypto/engines/RijndaelEngine.java
-       cp -f $(srcdir)/upstream/classes/org/bouncycastle/crypto/engines/RijndaelEngine.class $@
-upstream/src/org/bouncycastle/crypto/test/RijndaelTest.class: upstream/src/org/bouncycastle/crypto/test/RijndaelTest.java 
-       cp -f $(srcdir)/upstream/classes/org/bouncycastle/crypto/test/RijndaelTest.class $@
+# upstream/src/org/bouncycastle/crypto/engines/RijndaelEngine.class: upstream/src/org/bouncycastle/crypto/engines/RijndaelEngine.java
+#      cp -f $(srcdir)/upstream/classes/org/bouncycastle/crypto/engines/RijndaelEngine.class $@
+# upstream/src/org/bouncycastle/crypto/test/RijndaelTest.class: upstream/src/org/bouncycastle/crypto/test/RijndaelTest.java 
+#      cp -f $(srcdir)/upstream/classes/org/bouncycastle/crypto/test/RijndaelTest.class $@
 
 JAVAX_CLASSFILES = $(lib_javax_crypto_la_SOURCES:.java=.class)
 
--- ./upstream/src/org/bouncycastle/crypto/engines/RijndaelEngine.java~ Thu Jun 14 22:15:30 2001
+++ ./upstream/src/org/bouncycastle/crypto/engines/RijndaelEngine.java  Fri Oct  5 19:57:12 2001
@@ -297,7 +297,11 @@ public class RijndaelEngine
             throw new IllegalArgumentException("Key length not 182/192/256 bits.");
         }
 
-        switch (keyBits >= blockBits ? keyBits : blockBits)
+       // This is a work-around for java/4489
+       // http://gcc.gnu.org/ml/java-prs/2001-q4/msg00005.html
+       int temp_switch_expr = keyBits >= blockBits ? keyBits : blockBits;
+
+        switch (temp_switch_expr)
         {
         case 128:
             ROUNDS = 10;

      reply	other threads:[~2001-10-05 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-23  8:52 Anthony Green
2001-10-05 21:21 ` Alexandre Petit-Bianco [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=15294.34486.581237.51727@fencer.cygnus.com \
    --to=apbianco@cygnus.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).