10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
This bit of code works fine:
egrep -i '^rmcat' /etc/oratab |\
awk -F\: '{print $1}'|\
while read ORACLE_SID
do
But when I modified it, thus:
egrep -v '^#' /etc/oratab |egrep -v '^$' | egrep -v '^listener' \
awk -F\: '{print $1}'|\
while read ORACLE_SID
do (3 Replies)
Discussion started by: edstevens
3 Replies
2. Shell Programming and Scripting
Hi all.
Long time!!
Hope you're doing well..
I've stumbled on a peculiar siutaion here, and would expect help from this forum on a clean resolution.
We are running an rm and find command simultaneously from two different Unix sessions of the same user(let's say USER01) and on the same... (3 Replies)
Discussion started by: kumarjt
3 Replies
3. Programming
Hello,
This is related to the closed post in the forum for the installation of the same software called arachne, but with different error message:
In file included from ueberal/MiniSuperizer.cc:5:0:
./random/GnuRandom.h:54:5: error: ‘_G_uint32_t’ does not name a type
_G_uint32_t u;
^... (11 Replies)
Discussion started by: yifangt
11 Replies
4. UNIX for Dummies Questions & Answers
Hi guys,
I have a question. In the passwd file, user johndoe has a GID of 100 which is the group named users in the group file. But if you check the group file, johndoe is not listed under GID 100, but under GID 33, which is the group named videos. Under what group does johndoe really belong,... (1 Reply)
Discussion started by: goldenlight1814
1 Replies
5. Programming
I am getting confused compiling a program that gives me the following error
../../../tomso/algeb/vector.hpp:19:9: error: ‘Vector' does not name a type
typedef Vector<float> Vecflt; (1 Reply)
Discussion started by: kristinu
1 Replies
6. Programming
Hi!
This is part of my my code :
typedef struct{
int x;
char na;
char sur;
} Stu;
typedef struct{
Stu *arr;
int size;
int sort;
} Stus;
I want to ask how can i free() the matrix arr.
I tried free(arr), free(Stus.arr) and i get errors with gcc.
My problem, in... (3 Replies)
Discussion started by: giampoul
3 Replies
7. Programming
I've google a bit about this and couldn't find an answer. Actually I read that it can't be done.
Basically I've defined the following structure and typedef it as follows.
stuct Name {
};
typdef struct Name Name.
and right after it, defined some API that use it.
void blabla(Name*... (6 Replies)
Discussion started by: emitrax
6 Replies
8. Solaris
AIM- Install Oracle 11g on Solaris using VMWare
Steps
1.Logged on as root
2.Created subfolders à /usr/local/bin & /usr/local/bin/gcc
3.Downloaded gcc & libiconv & unzipped them on my harddrive & burnt them on CD
4.Copied files from CD to /usr/local/bin/gcc
5.Terminal (root) à pkgadd -d... (8 Replies)
Discussion started by: Ackers
8 Replies
9. Programming
I want to declare
char ch as ch_9 with the help of the typedef statement.
Thanks (1 Reply)
Discussion started by: krishna_sicsr
1 Replies
10. HP-UX
my pragram runs with 3 threads, 2 work threads, one main thread. the 2 work threads run with the same mode and the same code. but now, one of the work thread can't work, and it uses the cpu more than 80%, sometimes uses 100% cpu resource. the another work thread work well.
when I viewed the HP... (2 Replies)
Discussion started by: happylife365
2 Replies
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)
