Re: Linux X demo

On Jul 19, 8:48 am, Frank Kotler <fbkot...@xxxxxxxxxxx> wrote:
santosh wrote:
On Thursday 19 Jul 2007 4:11 pm, Frank Kotler <fbkot...@xxxxxxxxxxx>
wrote in message <EdHni.5682$bP4.2953@trndny01>:

"santosh" <santosh....@xxxxxxxxx> wrote in message
news:f7n54g$mv1$1@xxxxxxxxxxx

[ ... ]

<http://137.193.64.130/windela.zip>

Or search the group for more links.
IIRC instructions are implemented only uptil the 486, and the
compile crashed for me on Linux.

I found I had to rename the file to a lower-case ".c" before it
would compile with gcc (Linux). Upper case ".C" implies C++, or
some nonsense. Compiled and worked fine for me. (yeah, "-Wall
-pedantic" makes gcc complain... so don't)

Oops. Excuse my stupidity.

It was news to me, too. Very little stupidity around here. Most of us
are pretty smart (and almost all of us think we are). But all of us are
smarter than any of us!


What?? Nobody read 'man' pages anymore?? I'm surprised that santosh
didn't know this one.

<clip>
Options Controlling the Kind of Output

Compilation can involve up to four stages: preprocessing,
compilation
proper, assembly and linking, always in that order. GCC is
capable of
preprocessing and compiling several files either into several
assembler
input files, or into one assembler input file; then each
assembler
input file produces an object file, and linking combines all
the object
files (those newly compiled, and those specified as input) into
an exe-
cutable file.

For any given input file, the file name suffix determines what
kind of
compilation is done:

file.c
C source code which must be preprocessed.

file.i
C source code which should not be preprocessed.

file.ii
C++ source code which should not be preprocessed.

file.m
Objective-C source code. Note that you must link with the
libobjc
library to make an Objective-C program work.

file.mi
Objective-C source code which should not be preprocessed.

file.mm
file.M
Objective-C++ source code. Note that you must link with
the
libobjc library to make an Objective-C++ program work.
Note that
.M refers to a literal capital M.

file.mii
Objective-C++ source code which should not be preprocessed.

file.h
C, C++, Objective-C or Objective-C++ header file to be
turned into
a precompiled header.

file.cc
file.cp
file.cxx
file.cpp
file.CPP
file.c++
file.C
C++ source code which must be preprocessed. Note that
in .cxx, the
last two letters must both be literally x. Likewise, .C
refers to
a literal capital C.

file.hh
file.H
C++ header file to be turned into a precompiled header.

file.f
file.for
file.FOR
Fortran source code which should not be preprocessed.

file.F
file.fpp
file.FPP
Fortran source code which must be preprocessed (with the
tradi-
tional preprocessor).

file.r
Fortran source code which must be preprocessed with a
RATFOR pre-
processor (not included with GCC).

file.f90
file.f95
Fortran 90/95 source code which should not be preprocessed.

file.ads
Ada source code file which contains a library unit
declaration (a
declaration of a package, subprogram, or generic, or a
generic
instantiation), or a library unit renaming declaration (a
package,
generic, or subprogram renaming declaration). Such files
are also
called specs.

file.adb
Ada source code file containing a library unit body (a
subprogram
or package body). Such files are also called bodies.

file.s
Assembler code.

file.S
Assembler code which must be preprocessed.

other
An object file to be fed straight into linking. Any file
name with
no recognized suffix is treated this way.

You can specify the input language explicitly with the -x
option:

-x language
Specify explicitly the language for the following input
files
(rather than letting the compiler choose a default based on
the
file name suffix). This option applies to all following
input
files until the next -x option. Possible values for
language are:

c c-header c-cpp-output
c++ c++-header c++-cpp-output
objective-c objective-c-header objective-c-cpp-
output
objective-c++ objective-c++-header objective-c++-
cpp-output
assembler assembler-with-cpp
ada
f77 f77-cpp-input ratfor
f95
java
treelang

-x none
Turn off any specification of a language, so that
subsequent files
are handled according to their file name suffixes (as they
are if
-x has not been used at all).

<clip>

Nathan.

.

Relevant Pages

  • Re: Forth 200X and the Hayes tester
    ... compilation can work with minimal changes to source code. ... the assumption that programmers could be confused. ... standard names for some routines) to handle it. ...
    (comp.lang.forth)
  • Re: Standard Ada Preprocessor (Was: why ada is so unpopular ?)
    ... Some form of conditional compilation would make the job easier. ... sure there is a good answer, but Ada ought to try to address it somehow. ... the preprocessing of C code has made C the clear ... > the same level of portability. ...
    (comp.lang.ada)
  • Re: pgm object/source comparison
    ... There may be plenty of reasons why compilation fails, ... ILE, like default activation groups, objects ... I moved the libraries, files and ... >>> seems fairly obvious that the source code in those two don't match ...
    (comp.sys.ibm.as400.misc)
  • RE: Create an .exe at runtime with .NET 2.0
    ... for an example how I can compile a new executable with the encrypted file ... Model that enables developers of programs that emit source code ... 'Dynamic Source Code Generation and Compilation' ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.general)
  • Re: The Case Against RosAsm (#6)
    ... I used to wonder why people split up their source code in various source ... > RosAsm Doesn't Do Libraries ... > compilation for other reasons than ...
    (alt.lang.asm)