Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 94065 - gnu-crypto needs a fix to compile with JDKs >=1.5
Summary: gnu-crypto needs a fix to compile with JDKs >=1.5
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords: InVCS
: 98179 137003 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-05-26 04:58 UTC by Mikael Cluseau
Modified: 2006-06-16 10:54 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Path to create a working gnu-crypto-2.0.1-r1 ebuild (gnu-crypto.patch,4.43 KB, patch)
2005-05-26 05:00 UTC, Mikael Cluseau
Details | Diff
Raw patch to apply to on the sources. (java-5.patch,1.51 KB, patch)
2005-05-26 05:01 UTC, Mikael Cluseau
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Mikael Cluseau 2005-05-26 04:58:34 UTC
gnu-crypto fails to compile with JDKs >=1.5, here is a patch to make it work
(consistently with it's old behaviour).

Reproducible: Always
Steps to Reproduce:
1. emerge '>=sun-jdk-1.5'
2. emerge =gnu-crypto-2.0.1

Actual Results:  
10 errors at compilation.

Expected Results:  
0 errors at compilation
Comment 1 Mikael Cluseau 2005-05-26 05:00:35 UTC
Created attachment 59867 [details, diff]
Path to create a working gnu-crypto-2.0.1-r1 ebuild

applies from the dev-java directory. Use patch -p1 to use in the gnu-crypto
directory.
Comment 2 Mikael Cluseau 2005-05-26 05:01:30 UTC
Created attachment 59868 [details, diff]
Raw patch to apply to on the sources.
Comment 3 Jan Brinkmann (RETIRED) gentoo-dev 2005-05-28 16:58:07 UTC
patch now in cvs, thanks for your effort.
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2005-07-07 01:08:08 UTC
*** Bug 98179 has been marked as a duplicate of this bug. ***
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2006-06-16 10:54:35 UTC
*** Bug 137003 has been marked as a duplicate of this bug. ***