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

Tcl 8.2 requires Expect 5.31. Either upgrade to Expect 5.31 or go back to Tcl 8.0. (I recommend upgrading.)

I've rarely found the time to port Expect to alphas and betas. I recommend you stick with a production release unless you're willing to do some work.

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.

Debian uses the terminfo database and the ncurses library of terminal interface routes, rather than the termcap database and the termcap library. Users who are compiling programs that require some knowledge of the terminal interface should replace references to libtermcap with references to libncurses. To support binaries that have already been linked with the termcap library, and for which you do not have the source, Debian provides a package called termcap-compat.

The short answer is: lots of errors. If you think of the compiler as a tool for finding your programming mistakes, with the generation of runnable Z-code as a fortuitous by-product, you'll be close to the mark. Just occasionally a compilation is successful, but that's the exception rather than the rule; it's much more likely that it will fail, probably producing a lot of obscure messages. So, you should be neither surprised nor worried by a mass of error reports.

The Fortran header file you include has to be preprocessed before the Fortran file can use it. To have the cpp process the file before sending the file to the compiler, add the -F flag. For example:

He's specified the environment, he's read the FAQ, he's showing the error, and he's not assuming his problems are someone else's fault. This guy might be worth some attention.

If you encounter a "No Compiler Available" message, DrJava was not able to find a compatible copy of the "tools.jar" file, which comes with the Java SDK and contains the Java compiler. Note that versions of Java prior to 1.4 are not supported in the latest DrJava releases. You can specify the location of "tools.jar" by choosing "Preferences" from the Edit menu, choosing the "Resource Locations" section, and entering the location into the "Tools.jar Location" field. (The "..

The RPGIII compiler is limited to approximately 20,000 source statements. Because RTPA expands the source code, the resulting source code may exceed the limits of the RPG compiler. In that case, you can reduce the amount of information you audit by choosing a different audit profile or overriding the current audit profile.

Note that as of today (Sept 23 2000), only the RedHat distribution is supported by Vovida. It *may* work with other distributions. The quickest way to get around is to send an email describing your problem on the Vovida SIP mailing-list, all this after having check the mailing list archive, of course.

No, sorry. For starters, liballeg.a is about 450k, but you'd probably also want various utilities like the grabber, sound setup, etc. And what about all the example programs? If I included compiled versions of everything, a binary distribution would be over 7 megs: way too big to be practical! More seriously though, there just isn't any reason why you can't build it yourself.

Why does the compiler generate undefined symbols for functions taking pointer to functions? [C_PLUS_PLUS 4087]

Pine has been tested and compiles just fine on a suitably equipped SCO Unix 3.2.4, and probably works on the whole 3.2 series (testing has not been as extensive). It handles both MMDF and sendmail mailboxes without needing recompilation. It should be sufficient just to unpack the source tree and run "sh build sco" at the top level. You need to own the complete Development System, and the Developer's Versions of the other packages. Pine will not compile without TCP/IP support.

Most of the times, the environment variables are not set correctly. Please check if the following variables are set in your environment before trying to compile it: ANT_HOME -> should be set to the directory where you put ANT (for instance, /usr0/local/apache-ant-1.6.1) CLASSPATH -> should be set according to the directions in $MINORTHIRD/script/setup.xx file.

If you have a binary package which does not install correctly, or if you have trouble while following the instructions, then send a full bug-report to our bug list. Of course you can also write to the lilypond-user list for help.

I have a previous intall of jGRASP on my computer, but when I installed the new version it gives me an error when I try to compile.

You can compile anything you like, though on your own compiled programs will be delivered no support. When you want a library to be installed and it is in the FreeBSD package tree I suggest you request that one, instead installing one of your own, still my suggestions won't limit you on doing so.