You can compile the source code simply with any (Sun-compliant) java compiler, or use ant, or an IDE. Check out the Wiki article about Compiling Weka, which contains links to further articles, covering topics about ant and IDEs.

Contributions (or links to them) can be either posted to the Weka mailing list or sent to the Weka maintainer (normally also the admin of the Weka homepage). The conditions for new classifiers (schemes in general) are that, firstly, they have to be published in the proceedings of a renowned conference (e.g., ICML) or as an article of respected journal (e.g., Machine Learning) and, secondly, that they outperform other standard schemes (e.g., J48/C4.5). See similar questions...

If you run the classifier weka.classifiers.functions.LibSVM and get the libsvm classes not in CLASSPATH! error message, you are missing the libsvm jar archive in your current classpath. The LibSVM classifier is only a wrapper for using the libsvm classes. Check out the LibSVM article on the Wiki for details about how to use this classifier. See similar questions...

It's not that hard to use Weka classes in your own code, the following articles give a good overview of how to do that: In general, the articles of the source code category. Note: Weka is open-source software under the GNU General Public License, which means that your code has to be licensed under the GPL as well. See similar questions...

Yes, you can. Read the Use Weka with the Microsoft .NET Framework article on the Wiki. There is also a tutorial for IKVM available. See similar questions...

brings a new and exciting answer to this question: PAR, a "Cross-Platform Packaging and Deployment tool", originally developed by Autrijus Tang. Before PAR, the only public support for Perl/Tk "compilation" was in the Dr. See similar questions...

Edit the code and remove the arguments to setpgrp. Or upgrade to Expect 5.31 (or later) which adapts automatically. See similar questions...

Check this out: Cobalt Raq2 - Building expect causes Fatal signal 11 in gcc [Kernel 2.0.34 MIPS , Redhat/Cobalt Release 4.0] Seems libieee.a is built oddly and gcc doesn't like it, neither expect nor tcl seem to actully need it, removing -lieee from the makefile allows it to compile, no undefined references, expect passes make test... (Maybe the needed functions are really in libm?) ps: tcl 8.2.1 needs the same fix to compile See similar questions...

REG) See the Kernel HOWTO for some information. Also, there are people at http://www.kernelnewbies.org/ who are usually willing to help. William Stearns) The Buildkernel script walks you through an entire kernel build, including downloading the necessary files, patching the source, building the kernel and modules, installing the lot into lilo, and optionally building pcmcia-cs, cipe, and freeswan code for that kernel. See similar questions...

You need Visual C++ 6 and Sleepycat db 3.1.17 (which you can get from here). If the compiler complains about missing db.h, then you don't have Sleepycat in a place where the compiler expects to find it. The project files for Outport are set up such that it expects the Sleepycat db zip file to be expanded in a directory called db-3.1.17, as in the diagram to the right. When you compile it, the binaries are created in win32/bin and win32/bind (release and debug respectively). See similar questions...

This might be either because it's completely unknown or because the specific environment (include files, OS version, et cetera) isn't explicitly handled. If this happens, you may need to port the server to your OS yourself. Some operating systems include a default C compiler that is either not ANSI C-compliant or suffers from other deficiencies. The usual recommendation in cases like this is to acquire, install, and use gcc. See similar questions...

Solaris (2.5 and up) has its own version of X in /usr/openwin, its own version of make in /usr/ccs/bin/make, and its own compiler (to be purchased separately) which, if you have it, is available in /opt/SUNWspro/bin. Solaris does not provide the XPM library, which is required for the Xaw client; it doesn't provide any of the stuff required for imlib, gdk and gtk, either, which is required to build the GTK+ client. See similar questions...

On Solaris, FreeBSD, and some other systems, the default make isn't GNU make. In order to compile with such a make you must either configure --disable-cvs-deps --disable-nls in order to disable the GNU make specific parts of the Makefile. See similar questions...

If your operating system is from Sun or HP examine the Makefile and make any changes indicated inside. Copy the sample configuration file (sconfig.txt) to some convenient place such as /usr/local/lib/junkbuster/configfile or whatever you choose. The sample file has all the options commented out. You can remove the # character on any that you want, but it may be better to leave this until to later. Run it asynchronously: Decide on the options you really want, kill the process and start it again. See similar questions...

If you're not used to compiling code yourself, ask your ISP or administrator at work to provide it for you, or wait until we release an executable version. This is scheduled for mid-October 1997. Download zip file called ijb20.zip (~140k), then uncompress and unpack the zip archive using a tool like WinZip. Now the distribution (source and sample files) will be in a directory called ijb20. See similar questions...

LOADEST users running Linux or Windows on personal computers or Solaris on Sun Workstations can use the pre-compiled executables that are available in the Download section of this Web site; compilation for these operating systems/hardware platforms is not required. Executable files are not available for your specific operating system/hardware platform (Macintosh computers, for example). See similar questions...

Once the system starts compiling, a status window will be displayed. The compile is complete when the status window displays: Compile successful: Press any key See similar questions...

For versions prior to 1.5.2: Ensure that you are using Visual Studio 6 and have the latest service pack (at least sp5 - if you get error C2440 you need this), also ensure that you have the latest Microsoft Platform SDK (the one that comes with Visual Studio is dated and does not work with AxCrypt - you may receive errors about undefined symbols and also errors in templates used for safe Handle-handling in AxCrypt). For versions 1.5. See similar questions...

Weka not only uses the .props files that are present in the jar archive, but also the ones in the user's home directory and the current directory, i.e., the one Weka was started from. For a complete overview, see the section Precedence in theProperties file article. See similar questions...

You may have an application that's not error-free; or (more likely) one which needs configuration for your site, computer platform, etc. If it's not a bug within the application it probably has to do with your compiler options. If it's indeed that, there are several possibilities. In the examples we'll give now, we'll be using some installation directories that may differ from your installation. See similar questions...