On Wed, 21 Feb 2001 [EMAIL PROTECTED] wrote:
>
> Can you please tell me where i can find eCos ?
>
> Med venlig hilsen / Best regards
> Dan Net A/S
>
> Benjamin Petersen
> Systemudvikler
Sure, try:
http://sources.redhat.com/ecos/
Mo DeJong
Red Hat Inc
VSROOT :pserver:[EMAIL PROTECTED]:/cvs/jikes
cvs login
paswsd anoncvs
cvs checkout jacks
cheers
Mo DeJong
Red Hat Inc
Could someone add this patch to the configure script?
It just prints the available threading systems.
Mo DeJong
Red Hat Inc
Index: configure.in
===
RCS file: /cvs/kaffe/kaffe/configure.in,v
retrieving revision 1.146
diff -u
se that shipped with my Red Hat 6.2 system
is really showing its age. There are plenty of bugs that
have already been fixed in the CVS. I am going to do a CVS
update and run some regression tests right now.
later
Mo DeJong
Red Hat Inc
hen reply with)
auth subscribe jacks EMAIL
After you have subscribed, you can post messages
to [EMAIL PROTECTED]
cheers
Mo DeJong
Red Hat Inc
extensions/tools/javalib/kaffe/tools/jar/Jar.java
Mo Dejong
Red Hat Inc.
If we
160 * have been resolved then we just return the answer.
161 */
162 lockClass(this);
This call to lockClass() is where things get deadlocked. I guess I just
do not understand how this thread is going to be woken up after it goes
to sleep with no timeout.
Any ideas?
Mo DeJong
Red Hat Inc
e. Then you just cd to the kaffe directory run
./configure ; make ; make install and it should
build and install.
I have not tested this myself so you may run into problems
but that is how it "should" work.
Mo Dejong
Red Hat Inc.
I also found this note in kaffe/FAQ/FAQ.pthreads
* We do not support asynchronous exceptions via Thread.stop()
Mo Dejong
Red Hat Inc.
On Mon, 22 May 2000, Mo DeJong wrote:
> I was under the impression that methods like Thread.stop() were
> removed from the JDK or replaced with no-ops.
Here are some notes about it from the Sun developer site.
http://developer.java.sun.com/developer/bugParade/bugs/4187649.html
http://developer.java.sun.com/developer/bugParade/bugs/4248898.html
Mo Dejong
Red Hat Inc.
On 22 May 2000, Jason Baker wrote:
>
> Archie Cobbs <[EMAIL PROT
or this? I hate
to sound preechy but there are not many regression tests
for Kaffe and yet there seem to be lots of bugs getting
fixed. This is not a good thing. If every time a bug
got fixed, a regression test we added we would be a lot
better off.
> Problem now fixed.
>
> Thankyou.
>
> Nic
Mo Dejong
Red Hat Inc.
an not even finish a configure
if they are lacking a critical feature like zlib.
Mo Dejong
Red Hat Inc.
On Tue, 4 Apr 2000, Stuart Ballard wrote:
>
> Timothy Stack wrote:
> >
> > from kaffe/clib/zip/Inflater.c, line 17:
> >
> > #if defined(HAVE_LIBZ) &&
new net release is
a lot better than the B.20 release.
Mo Dejong
Red Hat Inc.
On Wed, 19 Apr 2000, Jim King wrote:
>
> Hello,
>
> I am a Win32 JVM developer. Though I succeeded in building and running
> Kaffe 1.0b3 on Cygwin one year ago, I failed to running Kaffe 1.0.5.
> After
On Wed, 12 Apr 2000, Chris Gray wrote:
>
> On Tue, 11 Apr 2000, Mo DeJong wrote:
>
> > The "best" thing for you to do is write your code on your desktop
> > with the Sun JDK 1.2 installed. Then when your code is finished
> > and you have created your
changes, run "cvs diff" and post your patch to the
list.
Mo Dejong
Red Hat Inc.
On Tue, 11 Apr 2000, Douglas De Couto wrote:
>
>
> hi,
>
> i tried to post this bug on the web site last night, but it didn't
> seem to work.
>
> When using kaffeh to emit jni h
o is write your code on your desktop
with the Sun JDK 1.2 installed. Then when your code is finished
and you have created your regression tests, compile and run the
same code on Kaffe (the GPLed version). If the code does not compile
with Kaffe, post a note to the list describing the problem. If you
can not fix it yourself, I am sure someone can help you figure
out how to fix it. If you can fix the problem yourself, then
fix the bug in Kaffe and send a patch to the list.
Mo Dejong
Red Hat Inc.
This patch fixes a bug that was added to StringBuffer recently.
It also adds some regressions tests for the bug and related calls.
Mo Dejong
Red Hat Inc.
Thu Apr 6 00:30:30 PDT 2000 Mo DeJong <[EMAIL PROTECTED]>
* libraries/javalib/java/lang/StringBuffer.java: fixed
s
The jar tool from 1.0.5 is completely busted. Don't even try
to use it. You need to most recent CVS snapshot if you want
to try to debug this.
Mo Dejong
Red Hat Inc.
On Mon, 3 Apr 2000, Stuart Ballard wrote:
>
> Apologies if this arrives twice - this is my first posting to the lis
Stream(entryfile);
ZipEntry ze = new ZipEntry(entryname);
ze.setMethod(ZipEntry.STORED);
readwriteStreams(in, zos); // this just writes all the data to in
zos.closeEntry(); // this closes the current entry on the ZipOutputStream
Any comments?
Mo DeJong
Red Hat Inc.
ore, it is not
accessible in class "tcl/lang/FileUtil".
The following patch fixes the problem.
Sat Apr 1 08:00:00 PST 2000 Mo DeJong <[EMAIL PROTECTED]>
* libraries/javalib/java/lang/StringBuffer.java: fixed
problem with ensureCapacity() method, it was acci
Could someone apply this patch? It cleans up some old code
and adds a new test case.
Thanks
Mo DeJong
Red Hat Inc.
diff -u -r1.1 ArrayForName.java
--- test/regression/ArrayForName.java 2000/02/29 22:59:42 1.1
+++ test/regression/ArrayForName.java 1999/12/11 14:51:22
@@ -137,6 +137,7
ight place to send compiler problem reports?
Mo Dejong
Red Hat Inc.
orking on some improvements
to my patch that would fix things once and for all. We should wait
for his improved patches and add them instead of my original patch.
I was unaware of this so I thought my original patch had been
lost in the shuffle.
Thanks
Mo Dejong
Red Hat Inc.
> "(Ljava/lan
On Tue, 29 Feb 2000, Archie Cobbs wrote:
>
> Mo DeJong writes:
> > I was just looking over the ChangeLog and I noticed that my
> > Class.forName() patches never got added. I seem to remember
> > that there was a problem with one of the changes in the patch.
> >
zip files.
Mo Dejong
Red Hat Inc.
// This class will write a zip file into memory and verify that the
// contents being written matches the expected output.
import java.io.*;
import java.util.*;
import java.util.zip.*;
public class ZipVerify extends ZipVerifyUtils {
public static
anyone
see any problems with the patch in its current form?
Mo Dejong
Red Hat Inc.
Index: kaffe/kaffevm/classMethod.c
===
RCS file: /cvs/kaffe/kaffe/kaffe/kaffevm/classMethod.c,v
retrieving revision 1.75
diff -u -r1.75 classMethod.c
/ZipVerify.java
test/regression/Makefile.am test/regression/Makefile.in: new
testcases.
Mo Dejong
Red Hat Inc.
On Mon, 14 Feb 2000, Edouard G. Parmelan wrote:
>
> Moses DeJong wrote:
>
> > Attached in a patch for
> > libraries/extensions/tools/javalib/kaffe/tools/jar/Ja
it into a Mauve test so you should not really need to add it.
Mo Dejong
Red Hat Inc.
> Thanks very much for your regression test.
>
> - Godmar
>
> >
> > It sounds like there is still some debate as to how the
> > primitive classes should be searched for by nam
right
way (assuming there is agreement on what that way is),
will the following test still work? If we can not search
by a class name like "void" then will there be macro
tests like CLASS_ISVOID() CLASS_ISINT() added so we can
do such tests?
if (strcmp(CLASS_CNAME(c), "void") ==
On that note, here is an updated regression test that takes care
of the case where you have an actual Class name "int" or "I" and
it also checks for / in the name of a class passed to forName().
Mo Dejong
Red Hat Inc.
On Tue, 1 Feb 2000, Godmar Back wrote:
> Let me
test check for this is to ensure that
a loaded class (like "int") is not a primitive type.
Mo Dejong
Red Hat Inc.
On Mon, 31 Jan 2000, Patrick Tullmann wrote:
> I ran ArrayForName on JDK 1.2.2 on Solaris. Got this output:
>
> for clsName "int" expected "Excepti
On Sun, 30 Jan 2000, Archie Cobbs wrote:
>
> Mo DeJong writes:
> > I have been working on getting Class.forName() working more like
> > the Sun JDK and I have a patch that I would like to get some comments
>
> I don't understand this comment:
>
> + /*
1035).
I am not sure if this would break JNI code, or if was just the wrong
place to make the change. Could someone who knows more about the
internals check it out and suggest a better change if there is one?
thanks
Mo Dejong
Red Hat Inc.
public class ArrayForName {
public static void
If you created the zip file with Kaffe's jar tool, then ZipOutputStream
is to blame. Try creating your zip file with zip and then uncompress it
with Kaffe's jar tool. If it is still broken, then it must be a problem
other than the one I was talking about.
Mo Dejong
Red Hat Inc.
On F
fix it once and for all. If you want to jump in and
take a whack at it, the problem is in the class ZipOutputStream.java!
Mo Dejong
Red Hat Inc.
On Fri, 28 Jan 2000, Hiroshi Oota wrote:
>
> ;; > I built Kaffe from CVS tree today under FreeBSD-3.4-RELEASE.
> ;;
> ;; >
35 matches
Mail list logo
