Sponsored Content
Top Forums Shell Programming and Scripting How to find our working compiler Post 18609 by s_aamir on Sunday 31st of March 2002 06:23:56 PM
Old 03-31-2002
How to find our working compiler

Hi, I am using Turbo Linux and needs to install Samba on it. But it said that could not find gcc. My question is how to find out which compiler is working on my system. I tried echo $CC but it gave me nothing. How can I set environmental compiler to c.
Thanks in advance.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

find command not working

Hi, Having issues with the . parameter in the find command. Issuing "find . -name \*.pl" gives me find: cannot open .: No such device I got it working by substituting . with *, so "find * -name \*.pl" gives the correct listing. bin/test.pl "which find" lists /bin/find. Anybody... (7 Replies)
Discussion started by: jabrady
7 Replies

2. Solaris

how to find which c/c++ compiler is used in solaris10

Dear Frnz Could you tell how to determine the c/c++ compiler version installed in the solaris 10/solaris 8. IT could be very helpful if you can tell me the pkg name also. Thanks (2 Replies)
Discussion started by: sriram.s
2 Replies

3. Programming

compiler can't find pstatus_t even procfs.h inlcuded

Hi, I am trying to get a the process cpu usage from the /proc file recently, on the Solaris 5.10. But met some rookie issue which i need some help. for below program, compiler complains that pstatus_t is undefined, although both type are defined in the procfs.h. #include <sys/procfs.h>... (4 Replies)
Discussion started by: sleepy_11
4 Replies

4. Shell Programming and Scripting

find | gawk --- NOT WORKING

Hi every1:) I have a problem with find and Pipe to gawk. Find -name '*.txt' -> works fine.. Gives all the txt file under home directory and sub directories But when I use it like this (see below). Find -name '*.txt' | gawk -F '\t' "script" :confused: It doesn't work.... (22 Replies)
Discussion started by: Needhelp2
22 Replies

5. Programming

How Can a Machine Reads a Compiler Since A Compiler is Written in Text! Not Binaries?

To make a programming language you need a compiler, so what was the first programming language and how was is created if you need the compiler first? The compiler itself is considered as a high language comparing to the machine! since the compiler is not created in 1's and 0's... Eventhough i... (12 Replies)
Discussion started by: f.ben.isaac
12 Replies

6. AIX

how to find out the compiler version and OS from binary file

Command to get the Compiler version(xlc/gcc) from the binary on AIX platform. I m searching for the Command, to get the Compiler(xlc/gcc) used to build the binary on AIX. I got two commands used on Linux Platform: - readelf -a <lib> | grep comment - hexdump -C -s 0x49e7b -n 1812 <lib> ... (1 Reply)
Discussion started by: Prajakta
1 Replies

7. Programming

how to find if C compiler in Solaris

Hi experts, How do I find if a C compiler is installed on Solaris ? > cc -o ksh: cc: not found > CC ksh: CC: not found > gcc ksh: gcc: not found I am using Solaris 5.8 Thanks, Sameer. (1 Reply)
Discussion started by: ensameer
1 Replies

8. UNIX for Advanced & Expert Users

Find and delete not working

Hi, I have a .ksh script which finds all the directories older than 84 days and tries to housekeep. Below is the command used find * -depth -type d -ctime +84 -exec rm -rf {} \; The above command lists all the directories ie child and parent directory in descending order which are more... (0 Replies)
Discussion started by: annamalai77
0 Replies

9. Shell Programming and Scripting

Find not working right

if ] then leftarray=($(find . -type l -printf "%p\n" 2>/dev/null)) rightarray=($(find . -type l -printf "%l\n" 2>/dev/null)) for var in "${rightarray}" do maximumarray=`echo "$var" | tr -dc "/" | wc -c | tr -d " "` index=$(($index+1)) done ############# for numbers in... (3 Replies)
Discussion started by: xpukm
3 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)
All times are GMT -4. The time now is 07:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy