Probably you are using the wrong C compiler. Grex has two compilers installed. cc is only used for building certain system executables. It is not ANSI standard, and it lacks certain standard include files. You need to use gcc instead. This is a fairly recent version of the Gnu C compiler. It is ANSI standard and very complete.

C++ is a superset of something, we're not sure what. You can use a C++ compiler to compile C code, but the results may surprise you.

I'm looking for new questions (with answers), better answers, or both. Please send suggestions to bug-octave@bevo.che.wisc.edu. If you have general questions about Octave, or need help for something that is not covered by the Octave manual or the FAQ, please use the help-octave@bevo.che.wisc.edu mailing list. This FAQ is intended to supplement, not replace, the Octave manual.

Not exactly; it can contain a pointer to another structure of the same type. Try: typedef struct { char *item; double *next; } NODEFAKE; typedef struct { char *item; NODEFAKE *next; } NODEPTR;

Almost any program with symbols can be probed. The "full support" described below is based on the debug information needed for source lines and target expressions. Support for additional architectures, operating systems and compilers is always in progress, so please contact if you don't see what you need here. Aprobe supports the Microsoft Visual C++ development system versions 6 and 7 but does not support .NET (Dynamic Runtime Model) applications.

The compiler only works for a small subset of Basic and produces quite inefficient code. I do not recommend it.

The C++ compiler generates old-style prototypes (no type information) for all functions, and the linker gives warnings in all of these cases. This will be alleviated in a future release of the C++ compiler. For now you can safely ignore warnings on parameter types in C++ compiled program.

You should use pkg-config's PKG_CHECK_MODULES macro in your configure.in file, as demonstrated in the gtkmm_hello package. Since this is the single most asked question about running GTK+ programs, we'll answer it here, even though it is in the GTK+ FAQ. Make sure the /usr/local/lib (the default install dir for gtkmm) is properly configured in your /etc/ldconf or that it is in your LD_LIBRARY_PATH environment variable. Alternatively, specify another prefix when running configure.

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

Yes; our J4-VDS hosting plan and above include the GCC compiler for building C and C++ applications, Perl modules, and other code from source.

For the "B" part (including the version in which you also return the pair of points along with the distance), you are expected to put your divide-and-conquer algorithm in a file called "closest-pair.cc" You will also need to modify lab1b.cc as indicated. A makefile is included with the provided code. Copy that into the directory with the rest of the code. Then just type "make". After successfull compilation and linking there will be a file called "lab1b.out". Just type "lab1b.out" to run it.

You should use forward slashes ("/") rather than backslashes ("\") in your #include filenames, even on operating systems that use backslashes such as DOS, Windows, OS/2, etc. For example: Note that you should use forward slashes ("/") on all your filenames, not just on your #include files. Note that your particular compiler might not treat a backslash within a header-name the same as it treats a backslash within a string literal.

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.

You should use the Compaq compiler fort to compile both your fortran 77 and fortran 90 programs. C and C++ programs can be compiled with gcc or g++, respecively. To compile and link your MPI programs to the MPI libraries, use mpif77, mpif90, or mpicc. The mpi scripts use fort to compile and link your fortran MPI programs, and gcc or g++ to compile and link your MPI C or C++ programs. You can compile your codes on any machine, and you do not need to submit a job to compile your codes.

Although Ch is designed to be a superset of C, like C++, there are some subtle differences between Ch and C. Therefore, some C programs straight out of a box may need to be polished to run in Ch. You should know the differences between Ch and C, before run a C program in Ch. The most common problems for running C programs straight out of a box in the Ch language environment at this point of implementation of Ch are as follows: Ch supports many new features in the latest C99 standard.

C++ class initialization such as myclass obj(i); is not valid in Ch. It can be replaced by myclass obj = myclass(i); which is valid in both C++ and Ch. More examples can be found below: myclass ob1 = myclass(i); // ok in both C++ and Ch myclass ob2 = myclass(2); // ok in both C++ and Ch myclass ob3(i); // ok in C++, bad in Ch myclass ob4(2); // ok in C++, bad in Ch

Where have you been? :-) Sun has dropped their old K&R C compiler, supposedly to create a market for multiple compiler suppliers to provide better performance and features. Here are some of the contenders: SunPro, SMCC, and various distributors sell a new ANSI-standard C compiler on the unbundled (extra cost) SPARCcompiler/SPARCworks CD-ROM. There are some other nice tools there too, like a "make tool" and a visual diff (interactive diff).

They've been programming more than ten years. You haven't. Draw your own conclusions. That's right! They hadn't noticed it. No doubt their compilers have it too, and its behavior is identical everywhere else in the world, also. That would explain everything.

From: libes (Don Libes) To: wren@io.nosc.mil Subject: Compile fails with: Don't know how to make pty_.c > I'm trying to compile Expect on hpux 9.01, > downloaded from ftp.cme.nist.gov expect.tar > after running config > the make fails with "Don't know how to make pty_.c. (compile fails) > I see three versions pty_sgttyb.c, pty_termios.c and pty_unicos.c in > the load, but the configure picked none of them. > I tried forcing to pty_termios.

My program is larger after upgrading to a newer version of the compiler. Why? A: When a new version of the compiler is released, all reported bugs from the previous version are fixed. Sometimes when a bug is fixed the resulting code can be slightly larger. If you find your program is slightly larger after upgrading, then it could be that your code would have been effected by the bug when compiled with the previous version.

Structs in C can certainly contain pointers to themselves; the discussion and example in section 6.5 of K&R make this clear. The problem with this example is that the NODEPTR typedef is not complete at the point where the "next" field is declared.  To fix it, first give the structure a tag ("struct node").

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.

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

In most cases, it is because you have an old version of a support library. The libraries needed to compile Dia version 0.91+ are: Pango version 1.1.5 or higher. Must be compiled with the PangoFT2 module. Pango 1.1.5 and higher depend on GLib version 2.1.3 or higher. PangoFT2 depends on font-config version 1.0.1 or higher. libunicode version 0.4 (not the version 0.7 available at SourceForge). Optional libraries that add extra features (for 0.

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 lines flagged by the assembler are the following, which use a combination of indirect operands and references to structure members: The MASM 5.11 assembler didn't mind this (and neither does Borland). But MASM 6.11 requires the use of the PTR operator to clarify the type of object pointed to by SI: If you're using ML.EXE, include the /Zm option when assembling. The complete command to assemble and link the program on page 269, for example, is: This message is generated when MASM.