Thread: [Aegisvm-devel] Win32 port of JPR
Status: Pre-Alpha
Brought to you by:
pwlfong
Menu
▾
▴
aegisvm-devel
|
From: Gildas B. <gb...@al...> - 2002-09-21 23:38:34
|
Hi Philip, Here are the patches for the Win32 port of JPR (minus the bits I already sent in my last mail). 1) jpr_win32.diff: the win32 port itself. It has been tested with both the MinGW and the MSVC (microsoft visual c++ compiler) compilers. 2) jpr_correctness.diff: various syntax fixes that MSVC needs in order to get rid of annoying warnings. 3) jpr_fp.diff: MSVC yells at this special case handling because there are divisions by 0, so I just conditionally disabled the offending code. 3) README.win32: file explaining how to compile JPR for win32 4) libffi.win32.patch: patch to make libffi compile under MSVC and a couple of fixes to have it compile under MinGW. (This patch hasn't been sent yet to the libffi maintainers but it will shortly). I also have patches pending for AegisVM but I need some sleep now so they will wait until tomorrow :) I hope you enjoy it :) -- Gildas |
|
From: Philip F. <pw...@us...> - 2002-10-17 00:39:43
|
Hi Gildas, I am trying to process your win32 port. Need to ask you for help with some configuration stuff. 1. I set up the mingw environment on my winME box. Somehow the cvs from msysDTK hangs whenever I perform cvs operations. It kind of performs the operation, but then does not known how to shut down. Have you experienced this anomaly before? I could have lived with WinCVS, but it is also buggy (it does not do cvs release), and I would hope to get my familiar command line cvs working. :-) 2. If I understand correctly, the patch to libffi is only for building libffi with MSVC and for cross-compiling from linux. So, I tried building a cvs version of libffi without your patch on mingw, but the configure script does not seem to be working on the mingw environment. What I am asking is, which snapshot of libffi are you using (e.g. date tag)? Would it be because I am using the wrong snapshot? Thanks for your help. I am really eager to merge your work into the cvs tree. :-) Philip On Sun, 22 Sep 2002, Gildas Bazin wrote: > Hi Philip, > > Here are the patches for the Win32 port of JPR (minus the bits I already > sent in my last mail). > > 1) jpr_win32.diff: the win32 port itself. It has been tested with both the > MinGW and the MSVC (microsoft visual c++ compiler) compilers. > > 2) jpr_correctness.diff: various syntax fixes that MSVC needs in order to > get rid of annoying warnings. > > 3) jpr_fp.diff: MSVC yells at this special case handling because there are > divisions by 0, so I just conditionally disabled the offending code. > > 3) README.win32: file explaining how to compile JPR for win32 > > 4) libffi.win32.patch: patch to make libffi compile under MSVC and a couple > of fixes to have it compile under MinGW. (This patch hasn't been sent yet > to the libffi maintainers but it will shortly). > > I also have patches pending for AegisVM but I need some sleep now so they > will wait until tomorrow :) > > I hope you enjoy it :) > > -- > Gildas -- Philip W. L. Fong pw...@us... The Aegis VM Project http://aegisvm.sourceforge.net The Aegis VM Project is an on-going effort to implement a lightweight, secure JVM. It will eventually feature a modular architecture, Proof Linking, that supports pluggable verification modules. |
|
From: Gildas B. <gb...@al...> - 2002-10-17 11:20:25
|
On Thursday 17 October 2002 02:39, Philip Fong wrote: > Hi Gildas, > > I am trying to process your win32 port. Need to ask you for help with > some configuration stuff. > > 1. I set up the mingw environment on my winME box. Somehow the cvs > from msysDTK hangs whenever I perform cvs operations. It kind of > performs the operation, but then does not known how to shut down. > Have you experienced this anomaly before? I could have lived > with WinCVS, but it is also buggy (it does not do cvs release), > and I would hope to get my familiar command line cvs working. :-) To be honest, I never tried the cvs included with msysDTK so I don't know, it might have a problem. Lately, I have been expermimenting with cygwin (www.cygwin.com). Cygwin is a quite stable environment and I know for sure its cvs command is working fine. Theoretically, you should also be able to use cygwin to build JPR and AegisVM, although I'm pretty sure you'll have to make a few changes to the build system (and I haven't tried myself). One of this changes would be to use CC="gcc -mno-cygwin" in order to build to build an exectuable which isn't dependant on the cygwin portability layer. > 2. If I understand correctly, the patch to libffi is only for building > libffi with MSVC and for cross-compiling from linux. So, I tried > building a cvs version of libffi without your patch on mingw, but > the configure script does not seem to be working on the mingw > environment. What I am asking is, which snapshot of libffi are > you using (e.g. date tag)? Would it be because I am using the > wrong snapshot? > Ah sorry, I forgot to tell you that you need to use the current cvs version of libffi (from http://sources.redhat.com/libffi/). This version already had some work done to support mingw32. > Thanks for your help. I am really eager to merge your work into > the cvs tree. :-) > Thanks for you time. -- Gildas |
|
From: Philip F. <pw...@us...> - 2002-10-22 21:04:14
|
Hi Gildas, I am trying very hard to merge your win32 port into the CVS tree, but I am having major difficulty setting up the environment on my winME box. The main thing is that I am not able to build the latest cvs snapshot of libffi. I tried several things: 1/ In the cvs checkout there is a copy of configure script. If I use it directly, it complains missing a certain ./../config-ml.in. Obviously, the setting of $libffi_basedir was messed up inside the configure script. 2/ I then tried running automake/autoconf to regenerate the configure script. The ones that seem to work produce Makefiles that require the substitutions @CCAS@ and @CCASFLAGS@, which are not actually defined. With this broken Makefile, assembly fails. 3/ I even tried brute-force mutilating of the generated Makefiles and configure scripts, but nothing works. 4/ I tried working with the cross-compiler you suggested, same thing happened. 5/ I then tried doing a normal unix build on my linux box. The same things occurred, and so I conclude that it has nothing to do with the windows setup. Even building libffi for linux would not work. So, would you let me know exactly which CVS snapshot of libffi are you using (e.g. which date)? And which exact version of autoconf/automake did you use? Somehow, the latest snapshot of libffi doesn't like my autotools installation. Thank you in advance. I really look forward to merging your port into the cvs tree. Philip -- Philip W. L. Fong pw...@us... The Aegis VM Project http://aegisvm.sourceforge.net The Aegis VM Project is an on-going effort to implement a lightweight, secure JVM. It will eventually feature a modular architecture, Proof Linking, that supports pluggable verification modules. |
|
From: Philip F. <pw...@us...> - 2002-10-22 23:16:28
|
Hi Gildas, Sorry about the whining. I found a clean fix of the libffi problem. Their current version of configure.in/Makefile.am is likely broken. I'll include fixing instruction in your README file. Thanks. Philip On Tue, 22 Oct 2002, Philip Fong wrote: > Hi Gildas, > > I am trying very hard to merge your win32 port into the CVS tree, but > I am having major difficulty setting up the environment on my winME box. > The main thing is that I am not able to build the latest cvs snapshot > of libffi. I tried several things: > 1/ In the cvs checkout there is a copy of configure script. If I use it > directly, it complains missing a certain ./../config-ml.in. Obviously, > the setting of $libffi_basedir was messed up inside the configure > script. > 2/ I then tried running automake/autoconf to regenerate the configure > script. The ones that seem to work produce Makefiles that require > the substitutions @CCAS@ and @CCASFLAGS@, which are not actually > defined. With this broken Makefile, assembly fails. > 3/ I even tried brute-force mutilating of the generated Makefiles and > configure scripts, but nothing works. > 4/ I tried working with the cross-compiler you suggested, same thing > happened. > 5/ I then tried doing a normal unix build on my linux box. The > same things occurred, and so I conclude that it has nothing to do > with the windows setup. Even building libffi for linux would > not work. > > So, would you let me know exactly which CVS snapshot of libffi are you > using (e.g. which date)? And which exact version of autoconf/automake > did you use? Somehow, the latest snapshot of libffi doesn't like my > autotools installation. > > Thank you in advance. I really look forward to merging your port into the > cvs tree. > > Philip > > -- > Philip W. L. Fong pw...@us... > The Aegis VM Project http://aegisvm.sourceforge.net > > The Aegis VM Project is an on-going effort to implement a lightweight, > secure JVM. It will eventually feature a modular architecture, Proof > Linking, that supports pluggable verification modules. > > > > ------------------------------------------------------- > This sf.net emial is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote > _______________________________________________ > Aegisvm-devel mailing list > Aeg...@li... > https://lists.sourceforge.net/lists/listinfo/aegisvm-devel > -- Philip W. L. Fong pw...@us... The Aegis VM Project http://aegisvm.sourceforge.net The Aegis VM Project is an on-going effort to implement a lightweight, secure JVM. It will eventually feature a modular architecture, Proof Linking, that supports pluggable verification modules. |
|
From: Philip F. <pw...@us...> - 2002-10-23 19:02:37
|
Hi Gildas, Well, I tried my best, and libffi even seems to install properly, with only one seemingly innocent linker warning: some of the symbols are not defined! Trying to link the patched JPR against this version of libffi fails because of the missing symbols. Do you think you could use "make dist" to create a copy of your working libffi snapshot, so I could work with that? Otherwise, I really have run out of ideas as to how I could proceed. Also, if I understand correctly, your libffi patch is only needed for compiling with VC++, right? Thanks. Philip On Tue, 22 Oct 2002, Philip Fong wrote: > Hi Gildas, > > Sorry about the whining. I found a clean fix of the libffi problem. > Their current version of configure.in/Makefile.am is likely broken. > I'll include fixing instruction in your README file. Thanks. > > Philip > > On Tue, 22 Oct 2002, Philip Fong wrote: > > > Hi Gildas, > > > > I am trying very hard to merge your win32 port into the CVS tree, but > > I am having major difficulty setting up the environment on my winME box. > > The main thing is that I am not able to build the latest cvs snapshot > > of libffi. I tried several things: > > 1/ In the cvs checkout there is a copy of configure script. If I use it > > directly, it complains missing a certain ./../config-ml.in. Obviously, > > the setting of $libffi_basedir was messed up inside the configure > > script. > > 2/ I then tried running automake/autoconf to regenerate the configure > > script. The ones that seem to work produce Makefiles that require > > the substitutions @CCAS@ and @CCASFLAGS@, which are not actually > > defined. With this broken Makefile, assembly fails. > > 3/ I even tried brute-force mutilating of the generated Makefiles and > > configure scripts, but nothing works. > > 4/ I tried working with the cross-compiler you suggested, same thing > > happened. > > 5/ I then tried doing a normal unix build on my linux box. The > > same things occurred, and so I conclude that it has nothing to do > > with the windows setup. Even building libffi for linux would > > not work. > > > > So, would you let me know exactly which CVS snapshot of libffi are you > > using (e.g. which date)? And which exact version of autoconf/automake > > did you use? Somehow, the latest snapshot of libffi doesn't like my > > autotools installation. > > > > Thank you in advance. I really look forward to merging your port into the > > cvs tree. > > > > Philip > > > > -- > > Philip W. L. Fong pw...@us... > > The Aegis VM Project http://aegisvm.sourceforge.net > > > > The Aegis VM Project is an on-going effort to implement a lightweight, > > secure JVM. It will eventually feature a modular architecture, Proof > > Linking, that supports pluggable verification modules. > > > > > > > > ------------------------------------------------------- > > This sf.net emial is sponsored by: Influence the future > > of Java(TM) technology. Join the Java Community > > Process(SM) (JCP(SM)) program now. > > http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote > > _______________________________________________ > > Aegisvm-devel mailing list > > Aeg...@li... > > https://lists.sourceforge.net/lists/listinfo/aegisvm-devel > > > > -- > Philip W. L. Fong pw...@us... > The Aegis VM Project http://aegisvm.sourceforge.net > > The Aegis VM Project is an on-going effort to implement a lightweight, > secure JVM. It will eventually feature a modular architecture, Proof > Linking, that supports pluggable verification modules. > > > > ------------------------------------------------------- > This sf.net emial is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote > _______________________________________________ > Aegisvm-devel mailing list > Aeg...@li... > https://lists.sourceforge.net/lists/listinfo/aegisvm-devel > -- Philip W. L. Fong pw...@us... The Aegis VM Project http://aegisvm.sourceforge.net The Aegis VM Project is an on-going effort to implement a lightweight, secure JVM. It will eventually feature a modular architecture, Proof Linking, that supports pluggable verification modules. |
Thanks for helping keep SourceForge clean.
X