11-01-2007
Quote:
Originally Posted by
rimon
How do I get this to compile?
Looks like you need to predefine some macros so that to the compiler it appears in release mode.
If you are porting Windows code to HPUX 11.23 using gcc, have you first ported it to Linux using gcc? It reduces the number of unknowns.
Alternatively use HPUX's aCC.
10 More Discussions You Might Find Interesting
1. AIX
Hello all,
I am having a problem with the following program on AIX:-
// Namespace.cxx
#include <iostream>
using namespace std;
#include <iostream.h>
int main()
{
// cout<<"Hello world";
return 0;
}
On compilation:-
$ xlC Namespace.cxx... (0 Replies)
Discussion started by: gupta_ca
0 Replies
2. Programming
Hi All,
I facing the following compilation error; when I implementing the following logic.
ostrstream ostr;
ostr << (( scAxsm.getRecord( i ).getField( 2 ).getShort())%12)!=0?(( scAxsm.getRecord( i ).getField( 2 ).getShort())/12+1)
: (( scAxsm.getRecord( i ).getField( 2 ).getShort())/12) <<... (1 Reply)
Discussion started by: sweta
1 Replies
3. Programming
Hi,
While trying compile a C++ file in UNIX with gcc whose make rule involves the usage of
/usr/ccs/bin/as, I get the following error:
/usr/ccs/bin/as: No such file or directory
/usr/ccs/bin/as: error: write error on output file "<filename>.o"
*** Error code 1
clearmake: Error: Build... (2 Replies)
Discussion started by: smanu
2 Replies
4. Programming
I am compiling a software xchm on solaris 10.
First i run './configure'
There is no error.
But when i start compiling using 'gmake'
following error shown
/usr/local/include/wx-2.6/wx/x11/brush.h: In copy constructor `wxBrush::wxBrush(const wxBrush&)':... (3 Replies)
Discussion started by: mansoorulhaq
3 Replies
5. Shell Programming and Scripting
Hi...
I would like to create a program that can be easily ported between several Linuxes... Therefore I would like to avoid compilation and have the ability to run it as shell scripts runs...
My program need to call some system calls such as fork etc...
do you know a way to use them without... (1 Reply)
Discussion started by: yamsin789
1 Replies
6. Linux
Hello every one,
here i am attempting to compile a c++ module using gcc.it is throwing a error .
error:
====
> make -S dummyCHARGP
/usr/local/bin/gcc -g -DDEBUG -DMAT -I. -I/swtemp/usbs/cc/unix-ce/root/subsys/lib/Linux/ -I/opt/dce/include -I/opt/dce/include/dce ... (12 Replies)
Discussion started by: mannam srinivas
12 Replies
7. HP-UX
hello everyone,
here i am attempting to compile a c++ submodule.OS is HP-UX.
here i am getting the following error.
======================================
"Make: Don't know how to make compile. Stop."
===================================
could you pls somebody suggest why this error is... (2 Replies)
Discussion started by: mannam srinivas
2 Replies
8. Programming
state_field state_abvr = {
"AL","ALABAMA",
"AK","ALASKA",
"AZ","ARIZONA",
"AR","ARKANSAS",
"CA","CALIFORNIA",
"CO","COLORADO",
"CT","CONNECTICUT",
"DE","DELAWARE",
"DC","DISTRICT-OF-COLUMBIA",
"FL","FLORIDA",
"GA","GEORGIA",
"HI","HAWAII",
"ID","IDAHO",
"IL","ILLINOIS",... (1 Reply)
Discussion started by: jagan_kalluri
1 Replies
9. Programming
I am facing problem while migrating the c++ code from Linux to Solaris. In linux the code is absolutly compiled fine with GCC compiler but when i am using the same in Solaris it coomplains
bash-3.1$ gcc LibSip.h
gcc: Compilation of header file requested
The same command is working fine in... (2 Replies)
Discussion started by: mrupesh74
2 Replies
10. Programming
I am trying to compile thunar 1.8.4.
It is giving me this error.
configure: error: X Window system libraries and header files are required Ubuntu Mate 18.04 (2 Replies)
Discussion started by: drew77
2 Replies
LEARN ABOUT DEBIAN
fort77
FORT77(1) Linux Programmer's Manual FORT77(1)
NAME
fort77 - invoke f2c Fortran translator transparently, like a compiler
SYNOPSIS
fort77 [-c] [-g] [-v] [-k] [-P] [-cpp] [f2c option ...] [-L directory ...] [gcc-option ...] [link option ...] [-O optlevel] [-o out-
file] [-s] [-w] [-Wx,arg1[,arg2]...] file ...
DESCRIPTION
The fort77 script invokes the f2c command transparently, so it can be used like a real Fortran compiler. It can be used to compile For-
tran, C and assembler code, and to link it with the f2c libraries.
File arguments ending with .f are compiled as Fortran source files. Files which end with .P are passed through to f2c, and files ending
with .F are passed to the C preprocessor (invoked as "/lib/cpp -traditional") first. Any switches passed via -D will be passed to the pre-
processor. If the translation is successful, the resulting C files will be passed to cc for translation into an object file. Files ending
in .c, .C, .cc, .i, .s, .S, .m, .cc or .cxx are passed to the GNU C compiler directly; see gcc(1). All other files are passed to the
linker.
OPTIONS
-c Supress linking and produce an object ( .o ) file from each source file.
-g Include debugging information. -v Be verbose; supplying this twice will also tell the C compilers etc to be verbose.
-k Keep the C files generated by f2c around.
-cpp Pass Fortran code through the C preprocessor, as if filenames ended in .F.
-P Generate f2c .P files.
-Ldirectory
Include directory in the search for libraries in the final linking stage.
-o outfile
Send output to outfile.
-trapuv Have f2c generate code to trap uninitialized values.
-Wx,arg1[,arg2...]
Pass the argument[s] argi through to the subprocess x, where x can assume one of the following values: f for the f2c step, p for
the preprocessing step, c for the C compiler, a for the assembler (this is actually passed to the C compiler, too), and l for the
linker. As an example, defining a preprocessor constant for the C compilation step would be done with -Wc,-DUNIX=1. Specifying
the -f option to f2c would be done via -Wf,-f.
f2c option
fort77 passes through almost all f2c options: -C, -U, -u, -a, -E, -h, -P, -R, -r, -z, -I2, -I4, -onetrip, -!c, -!l, -!P, -!R, -ext,
-!bs, -W[n], -trapuv, -w8, -r8 and -w66.
gcc options
The following options are passed through to gcc: -f*, -W*, -U*, -A*, -m*, -S, -E, -v, -x, -pipe, -o, -I, -V, -b*, -p, -pg.
linker option
The options passed to the linking stage are -static, -shared, -v, -V, and -symbolic.
BUGS
To make debugging work, you need to set a breakpoint at MAIN__ before you start.
f2c This script automatically supplies the -I. option to f2c. Older versions of f2c may not support this.
This script is for the interaction of gcc and f2c; using it with another compiler will probably require modification.
The fort77 script does not strictly conform to Posix.2, because it acceppts long options with one leading slash. This is done for gcc com-
patibility.
SEE ALSO
f2c(1), cc(1), as(1), ld(1)
AUTHOR
Thomas Koenig, ig25@rz.uni-karlsruhe.de
Linux Nov 1996 FORT77(1)