C compiling

[juniorls]

I recently loaded SuSE on my intel comp.

I am presently taking a walk down memory lane from my days at UofT.

I was fiddling round with cc and the gcc compilers.

I wrote a basic basic basic program .

I tried to compile it as I remember doing in Uni. The problem is that it can't find the header file that I included in the program (studio.h). The compiler spits out the error message "studio.h: No such file or directory.



Where is this file located or do I have to load it from elsewhere?



Thanks.



PS:I did a search for studio.h and found no references.

More Information:

1. You will also get compiler issues related to the fact that most of them will have been tested using gcc and C compilers a notorious for being picky
2. In no particular order these are a few of the most significant ways in which C programs are compiled into CIL:
3. c but does not invoke the linker; the -c flag stops the process after compilation
4. You might want to activate some of the options at the start of the file by uncommenting the corresponding lines
5. First thing to do, of course, is to install 'dmake
6. When compiling a C program in Unix, why do I get "ld: Unresolved:"? When compiling a C program in Unix, an "ld: Unresolved:" error indicates that your program uses a symbol from a library which is not being linked
7. This chapter describes how to compile C programs using gcc
8. Accelerate applications on x64+GPU platforms by adding OpenMP-like compiler directives to existing Fortran and C programs
9. Did anyone here get Xerces-C to compile and work under MinGW
10. which is able to create Windows or console-based C/C++ programs using the Mingw compiler system (version MSVCRT 2

[snoopychuot]

It sounds like you may need to download the GCC library!?

More Information:

1. Since the 1970s it has become common practice to implement a compiler in the language it compiles, although both Pascal and C have been popular choices
2. Please note that the installation location of the libraries has changed, so developers on 64-bit Linux must update their LD_LIBRARY_PATH to contain either /usr/local/cuda/lib or /usr/local/cuda/lib64
3. distcc should always generate the same results as a local build, is simple to install and
4. 5 configure script won't be able to compile the little test program, aborting with this:
5. 1 Building environment; 2 Getting the dependencies; 3 Building libpano from SVN; 4 Building autopano-sift-c
6. However, I also wanted to make it work using distutils (as described here), which appeared to be the simplest method
7. Visual C++ 2008 includes a C compiler that you can use to create everything from basic C programs to Windows applications
8. When compiling with distcc the local system doesn't > show any kernel panic, while the same system used as a "remote compiler >
9. You're now done with the procedural part of compiling and running your first program with Xcode (whew!)

[lisusu]

did you use the include "" syntax

or the include <> syntax...

remember they have different meaning ...

More Information:

1. The disadvantage of compiling in a single pass is that it is not possible to perform many of the sophisticated optimizations needed to generate
2. If you have more than one file to compile, just do something like % cc foo
3. Christian Queinnec's Lisp in Small Pieces: is the Scheme-to-C bible
4. If you didn't get your extern "C" right, you'll sometimes get linker errors rather than compiler errors
5. If a program is useful and if the source code is available, sooner
6. LINQ's relationship to the new C#3 and VB9 features · Anders Hejlsberg, Herb Sutter, Erik Meijer, Brian Beckman: Software Composability and the