Re: [kaffe] problems compiling kaffe-1.1.6 with alsa-lib-1.0.11_rc2
Hi Joshua, I am not sure it is a kaffe bug or a alsa-lib bug (for having removed quietly two macro definitions). I have checked in a patch in cvs to verify that the two macros are defined before using them. It should not change the behaviour and make the code compile. Regards, Guilhem. Joshua Nichols wrote: Hey folks, Over in Gentoo land, we recently received a bug report [1] about kaffe-1.1.6 fails to compile against alsa-lib-1.0.11_rc2. Figured you guys would like to know. [1] http://bugs.gentoo.org/show_bug.cgi?id=119272 Regards, Josh Nichols Gentoo Developer ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
[kaffe] problems compiling kaffe-1.1.6 with alsa-lib-1.0.11_rc2
Hey folks, Over in Gentoo land, we recently received a bug report [1] about kaffe-1.1.6 fails to compile against alsa-lib-1.0.11_rc2. Figured you guys would like to know. [1] http://bugs.gentoo.org/show_bug.cgi?id=119272 Regards, Josh Nichols Gentoo Developer ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] Problems compiling Kaffe
On Mon, 07 Feb 2005 17:13:51 +0100, Dalibor Topic <[EMAIL PROTECTED]> wrote: > For 1.1.5, I think it would be easiest to simply make javac a wrapper > around jikes (or some other supported external compiler). Consider ecj as the compiler to wrap. Main advantage is full support of 1.5 language features *today* (and it doesn't require a 1.5 runtime to work either, as I've got it working under IKVM as I mentioned in my blog a while back). Stuart. -- http://sab39.dev.netreach.com/ ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] Problems compiling Kaffe
Fernando Lozano wrote: Hi Sanghyeon Seo, If Kaffe build really needs a Java compiler and Java VM, couldn't it use gcj / gij and so I could build it using only free software? jikes is a free software. What do you mean? But Sun, IBM or Blackdown JVMs are not, and I have not fould how to use gij as the JVM for comiling Kaffe. Jikes is not a Java VM, but just a Java compiler. Anyway it's strange that, to compile a Java VM, I need another Java VM. Yeah. Thanks for your bug report, I've fixed that now. And by the way, is kjc becoming unsupported? Not really. It won't return as a jar file, as jar files are not much fun to shuffle around in source tarballs. For 1.1.5, I think it would be easiest to simply make javac a wrapper around jikes (or some other supported external compiler). Kjc will return at the very latest post 1.1.5 as a supported external compiler. cheers, dalibor topic ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
some ideas on making packaging Kaffe easier (Was: Re: [kaffe] Problems compiling Kaffe)
Fernando Lozano wrote: Hi Sanghyeon Seo, If Kaffe build really needs a Java compiler and Java VM, couldn't it use gcj / gij and so I could build it using only free software? jikes is a free software. What do you mean? But Sun, IBM or Blackdown JVMs are not, and I have not fould how to use gij as the JVM for comiling Kaffe. Jikes is not a Java VM, but just a Java compiler. Anyway it's strange that, to compile a Java VM, I need another Java VM. Yeah, that's really bizarre. What are your configure flags, and where is the check happening? And by the way, is kjc becoming unsupported? It shouldn't become unsupported. I'm waiting to hear back from the authors of kjc. There was some confusion over whether Debian's packaging of our version of kjc.jar as it was in the Kaffe source tarball was according to the letter and the spirit of the GPL. While Kaffe.org is in compliance with the GPL, afaict, as the whole kjc source code to our modified version is available from the kjc module from the same place kaffe was distributed from, it wasn't clear whether Debian would have been, as the old kjc.jar apparently accidentally didn't contain its source code, and noone checked until now, apparently. Oops. :( So in order to avoid confusion, I quickly pulled kjc out of the CVS in hope that the authors of kjc would quickly comment on it, so that I could put it quickly back again. Unfortunately, the authors of kjc are very busy, so no reply has arrived yet. But after talking a bit more with Java packagers, and thinking about it for a while, I believe we'll have to think a bit more how to create a better way to distribute kaffe to make things easier and clearer for distributors and packagers, in order to avoid creating such confusion in the future. Stuffing jars into the CVS isn't such a great idea, so I started to eradicate them from our CVS. Right after kjc.jar, the second big thing to go was Klasses.jar.bootstrap, allowing me to extremely simplify the whole build system parts that depended on class library compilation. It's still not perfect (we still run a native kaffeh, where checking in pregenerated headers a la Classpath would be much friendlier to cross-compiling developers), but it's moving in the right direction. Make dist works again, and make distcheck also largely works fine, except for a few issues with left over files after cleanup. I've talked about that with Jim Pick and Ean Schuessler in the bug report on kjc[1], and the general idea for 'the future' is to eventually try to split kaffe the vm from the developer kit and eventually the class library when we're fully merged with classpath. That's something that SableVM and JamVM have been practising with pretty good success. Another idea propagated by JPackage packagers, who'd like to support kaffe in their distribution, is to have an extra java-kaffe-wrapper package, that takes care of creating the proper wrapper scripts and classes to make a full development environment, just like Thomas Fizsimmons' wrapper does that for gcj & ecj in the gcj wrappers in Fedora Core 4. It works pretty well for gcj, and it's an approach I think we should copy. Talking to David Walluck on IRC, I got the impression that JPackage packagers really don't like seeing binary blobs in packages, like prebuilt jar files. After making 'make dist' work again, it showed why: the pre-built rt.jar files and friends added around 8-9 megabytes to the tarball, a very sizeable chunk. So I started to simplify and rework the build system, and to rip things out the build system that are too complicated and take time to maintain. I'd really like to rip out the 'prebuilt rt.jar in the tarball' and friends, too, as they could equally well be distributed as jars from kaffe.org if anyone ever needs them. I hope I don't break things too heavily, and if I do I hope people will complain and yell and post patches :) So thanks for your bug reports, I appreciate your further comments, if any :) I'll try to make the build more friendly to free compilers other than jikes, and see to get that Java check kicked out, if you can help me find it. cheers, dalibor topic [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=291427 Arnaud is working on updated Kaffe and Kjc packages at the moment, though he is quite busy currently with 'real life', as well. :) ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] Problems compiling Kaffe
Fernando Lozano wrote: Hi there, I got Kaffe from CVS and tried to compile it myself but I cant understand why it needs jikes and whi it needs a Java VM. The configure script barks about these two pre-requisites. Wasn't Kaffe supposed to provide both a Java compiler and a Java VM? Hi Fernando, thanks for your bug reports! I don't recall the configure script checking for a Java vm. Could you post a snippet of the configure output? I think there was something like that in the configure script of gjdoc, I may have merged it in without thinking too hard about it and made a mistake, but I'm not sure. Kaffe shouldn't need an installed VM to build, if the configure script barks, then it's a bug. Regarding jikes: you need a java compiler to build the class library. Currently only jikes is supported in a user friendly way out of the box, I plan to add user-friendly support in the configure script for externally installed kjc, gcjx, ecj, gcj and javac soon. I could also find no info on how to use another Java compiler in place of jikes (wanted to use gcj). If Kaffe build really needs a Java compiler and Java VM, couldn't it use gcj / gij and so I could build it using only free software? gcj used to be pretty broken for compiling any class library other than it's own for a while. I haven't tried it on Kaffe's class library in ages, but I'll give it a go tonight, and try to add a --with-gjc option to the configure script. cheers, dalibor topic ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] Problems compiling Kaffe
Hi Sanghyeon Seo, If Kaffe build really needs a Java compiler and Java VM, couldn't it use gcj / gij and so I could build it using only free software? jikes is a free software. What do you mean? But Sun, IBM or Blackdown JVMs are not, and I have not fould how to use gij as the JVM for comiling Kaffe. Jikes is not a Java VM, but just a Java compiler. Anyway it's strange that, to compile a Java VM, I need another Java VM. And by the way, is kjc becoming unsupported? []s, Fernando Lozano ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
Re: [kaffe] Problems compiling Kaffe
On Wed, 02 Feb 2005 16:11:25 -0200, Fernando Lozano wrote: > If Kaffe build really needs a Java compiler and Java VM, couldn't it use > gcj / gij and so I could build it using only free software? jikes is a free software. What do you mean? ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
[kaffe] Problems compiling Kaffe
Hi there, I got Kaffe from CVS and tried to compile it myself but I cant understand why it needs jikes and whi it needs a Java VM. The configure script barks about these two pre-requisites. Wasn't Kaffe supposed to provide both a Java compiler and a Java VM? I could also find no info on how to use another Java compiler in place of jikes (wanted to use gcj). If Kaffe build really needs a Java compiler and Java VM, couldn't it use gcj / gij and so I could build it using only free software? []s, Fernando Lozano ___ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe
