08-09-2012
What do you mean by 'linking rule'? By the time code is linked, it's too late to do -DCOMPILE_SMP.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
This stems from the following thread https://www.unix.com/showthread.php?t=18299
I have a makefile which makes either executables or a shared library.
i.e. make -f unix.mak will create the executables and
make -f unix.mak libolsv will create the shared library.
Since these have to be... (4 Replies)
Discussion started by: vino
4 Replies
2. UNIX for Dummies Questions & Answers
I'm trying to define a variable named sin
I already have a variable named cos, which has the value "hello"
I want sin to have the value of "hellothere",
so sin would be something like
sin = $cos & "there"
but I'm not sure that I know the syntax.
Can anyone help?
:confused: (4 Replies)
Discussion started by: sailorliones
4 Replies
3. Shell Programming and Scripting
Hey all, I was wondering if someone would take a look at this script I'm working on. I don't know if i have the syntax correct for my variables and if the for loop is written correctly.
any assistance would be greatly appreciated.
#!/usr/bin/bash
###########################################... (12 Replies)
Discussion started by: em23
12 Replies
4. UNIX for Advanced & Expert Users
Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error:
make: module: command not found
Why is this? Is there any way to run this command in a Makefile?
NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 Replies)
Discussion started by: hernandinho
2 Replies
5. Programming
Is it possible to send a custom signal to a process?
e.g. Send signal 9999 to my process, which handles it with some custom handler.
How would one do this? (12 Replies)
Discussion started by: joha
12 Replies
6. Shell Programming and Scripting
I can't seem to get a rule in my Makefile to ever run... even if I change the rule to force make to re-enter the rule, or if I change the dependent files the rule depends on. Any ideas why the second rule is being ignored here?
#MAKEFILES = $(DIRS:%=$(ROOT)/%/Makefile)
#$(MAKEFILES):... (0 Replies)
Discussion started by: foureightyeast
0 Replies
7. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
Discussion started by: Tatl
1 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I have a trivial question but I dont know how to solve it.
So basically I'm working on a USB key and I have a directory with some scripts which I use to work on files present in other directories within the USB or sometimes on the main harddisk too. The problem is every time I have to... (3 Replies)
Discussion started by: pawannoel
3 Replies
9. Programming
I am trying to create a makefile to build a program and am getting the following error:
make -f tsimplex.mk
make: *** No rule to make target `/main/tsimplex_main.cpp', needed by `tsimplex_main.o'. Stop.
OPSYS = $(shell uname -s )
TARGET = tsimplex
ROOTDIR = ../../..
GTSDIR =... (1 Reply)
Discussion started by: kristinu
1 Replies
10. Shell Programming and Scripting
Hi all,
I want to know the entry point (default rule to be executed) in a makefile once all defined variables are evaluated. I do not have all: in my makefile and I give
"make" without any parameter in command line.
thanks........ (3 Replies)
Discussion started by: useless79
3 Replies
FC(1) General Commands Manual FC(1)
NAME
fc - frontend script to the f2c fortran compiler
SYNOPSIS
/usr/bin/fc [-o objfile] [-c] [-S] [-C] [-u] [-w] [-w66] [-D switch] [-I includepath] [-Ntnnn] [-P] files [-l library]
DESCRIPTION
fc is a script intended to be used as a front end to the f2c FORTRAN-to-C translator. It is supposed to make the whole f2c and C compiler
setup look like a real Fortran compiler.
File arguments with a .f suffix are compiled as Fortran source. Files with a .F suffix are passed through the C preprocessor cpp(1) first.
Files with .c (C source) or .s (assembly source) suffixes are passed to the C compiler directly. Files with a .e suffix are treated as efl
source files, and files with a .r suffix are treated as RATFOR source files.
OPTIONS
-o objfile
Produce an output executable named objfile rather than using the default name a.out.
-c Do not call the linker; instead, leave relocatable object files as *.o.
-S Produce assembly output as file.s
-C Compile in extra code to check that array subscripts are in bounds.
-l library
Libraries specified with this option are passed to the linker.
-U def Definitions specified with this option are passed to C compiler (for .c files) or to cpp (for .F files) to remove definition.
-u Complain about undeclared variables.
-v, --version
Print version of f2c in use
-w Omit all warning messages.
-w66 Omit Fortran 66 (Fortran IV) compatibility warning messages.
-D switch
The given switch is passed to the C compiler (for .c files), to cpp (for .F files) and to f2c.
-I includepath
Passed to the C compiler (for .c files), to cpp (for .F files) and to f2c.
-Ntnnn Allow nnn entries in table t.
-P Emit .P files.
BUGS
fc isn't really very good -- try fort77 (1), which does a better job.
This manual page isn't really very good either...
AUTHOR
S. Feldman, D. Gay, M. Maimone, N, Schryer are all mentioned in the paper on the conversion of Fortran to C.
Peter Maydell (pmaydell@chiark.greenend.org.uk) wrote this manual page, and Alan Bain (alanb@chiark.greenend.org.uk) made some minor modi-
fications.
SEE ALSO
f2c(1), fort77(1), cc(1), cpp(1), ratfor(1)
May 1999 FC(1)