Thank you Dapeng! I'll give it a try later today. Sun, Dapeng <dapeng....@intel.com> schrieb am Mi., 4. Mai 2016 um 05:33 Uhr:
> Hi Benedikt, > > Hope this information will be helpful > > 1. Upgrade openssl to 1.0.1c above using brew(http://brew.sh/)[1]: > Check your openssl version, by default it's not 1.0.1 > $openssl version > OpenSSL 0.9.8r 8 Feb 2011 > > $ brew search openssl > $ brew install homebrew/versions/openssl101 > $ brew link openssl --force > > Open a new terminal window, test your openssl version, it should be 1.0.1 > now > $ openssl version > OpenSSL 1.0.1s 1 Mar 2016 > If not, please check if Homebrew /usr/local/bin if at the front of $PATH > > 2. Download and install JCE Unlimited Strength Jurisdiction Policy Files[2] > > Download the Java Cryptography Extension (JCE) Unlimited Strength > Jurisdiction Policy Files from Oracle. > For JDK 1.6: > http://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html > For JDK 1.7: > http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html > For JDK 1.8: > http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html > > Uncompress and extract the downloaded file. The download includes a > Readme.txt and two .jar files with the same names as the existing policy > files. > > Replace local_policy.jar and US_export_policy.jar at > <java-home>/lib/security/ > > 3. Set system environment JAVA_HOME[3] > $ echo $JAVA_HOME > In Mac OSX 10.5 or later, Apple recommends to set the $JAVA_HOME variable > to /usr/libexec/java_home, just export $JAVA_HOME in file ~/. bash_profile > or ~/.profile. > > I have tried it on local machine, please feel free to let me know if you > still have any problem. > > Regards > Dapeng > > [1] > http://stackoverflow.com/questions/15185661/update-openssl-on-os-x-with-homebrew > [2] > https://www.attachmate.com/documentation/rweb/rweb-installguide/data/b1gdutii.htm > [3] > http://www.mkyong.com/java/how-to-set-java_home-environment-variable-on-mac-os-x/ > > -----Original Message----- > From: Benedikt Ritter [mailto:brit...@apache.org] > Sent: Wednesday, May 04, 2016 12:39 AM > To: Commons Developers List > Subject: Re: [CRYPTO] How to build CRYPTO on Mac OS 10.11? > > Chen, Haifeng <haifeng.c...@intel.com> schrieb am Di., 3. Mai 2016 um > 03:49 Uhr: > > > Sorry to not response in the past days due to Holiday here. > > We will start to check that. I agree that JNA is a good thing to try > > as long as the performance impact is in an acceptable level. > > > > It would be good enough for me to have some documentation on how to setup > the development environment. If none of the crypto developers uses Mac OS, > I'll need to figure out and document myself. Maybe somebody can help me via > hang out to understand better what the requirements are. > > Regards, > Benedikt > > > > > > > > -----Original Message----- > > From: sebb [mailto:seb...@gmail.com] > > Sent: Monday, May 2, 2016 6:51 PM > > To: Commons Developers List <dev@commons.apache.org> > > Subject: Re: [CRYPTO] How to build CRYPTO on Mac OS 10.11? > > > > On 2 May 2016 at 11:45, Benedikt Ritter <brit...@apache.org> wrote: > > > sebb <seb...@gmail.com> schrieb am So., 1. Mai 2016 um 21:19 Uhr: > > > > > >> On 1 May 2016 at 19:17, Benedikt Ritter <brit...@apache.org> wrote: > > >> > Hi, > > >> > > > >> > today I started working on the site build. I ran into problems > > >> > with the native build and with different JDK versions. Can anybody > help? > > >> > I've documented my problems in CRYPTO-45 [1]. > > >> > > >> I think you have discovered why there were concerns about using JNI... > > >> > > > > > > :-) > > > > > > I think it just has to be documented. The problem seems to be > > > specific to Mac OS 10.11. > > > > But it's not possible to document these problems without having access > > to the relevant OS. > > > > And even if one does, this is a non-trivial exercise as you have just > > shown. > > > > > > > >> > > >> > Regards, > > >> > Benedikt > > >> > > > >> > [1] https://issues.apache.org/jira/browse/CRYPTO-45 > > >> > > >> ------------------------------------------------------------------- > > >> -- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > >> For additional commands, e-mail: dev-h...@commons.apache.org > > >> > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > >
