03-17-2011
Hi.
My brief experiments suggest that targets in the first rule with syntax "%.o" will get compiled and the subsequent targets will be ignored. If this is true, then I assume your cpp rule comes before the fortran rule.
If this is the case with your makefile, you should be able to edit the makefile to place the fortran rule before the cpp rule and run make. I'm guessing that with that, the fortran will be compiled and the cpp ignored.
If my theory is true, then we can talk about how to solve the problem ... cheers, drl
( Edit 1: fixed typo )
Last edited by drl; 03-18-2011 at 12:11 AM..
10 More Discussions You Might Find Interesting
1. Red Hat
Hi,
i am trying to install AMBER10 which is a molecular dynamcis package onto two linux red hat pcs. I can successfully install the tools that comes with which uses gcc to compile, however AMBER10 requires either g95 or gfortran to compile. This is where the issue lies, i have installed both... (0 Replies)
Discussion started by: olifu02
0 Replies
2. Programming
How I can get the current make-file name in a make-file
So, if I run make with specified file:make -f target.mak
is it possible to have the 'target' inside of the that 'target.mak' from the file name? (2 Replies)
Discussion started by: alex_5161
2 Replies
3. Programming
Hi!
I have a program in fortran77. This program was compiled with pgf90, but now, I need compiled it with gfortran.
I show a bit of code.
program hello
PARAMETER(a=100)
integer a
write(*,*)'value ', a
end program hello
What's the problem?
Thanks (2 Replies)
Discussion started by: kekaes
2 Replies
4. Programming
Hi !
I have one program made of several sub programs which I am trying to compile with gfortran on Fedora 14 in my system. The program was originally written in Fortran 77 and compilation command used to be -
fort77 -O2 -f -w -o life life_com.f lifetime.f minuit.f tek_life.f utilities.f... (0 Replies)
Discussion started by: cylab123
0 Replies
5. Programming
Hi,
I am trying to run a simple f77 program on gfortran. Program is as follows.
program trial
implicit real*8 (a-h,o-z)
common/var/a(2),b,c(4),d
a=(/0,0/)
b=0
c=(/0,0,0,0/)
d=0
call add(a,b,c,d)
... (1 Reply)
Discussion started by: anshulfy
1 Replies
6. Programming
I am a INTEL fortran user recently migrated to linux and installed gfortran on my system.
I run numerical models as part of my research.
my question is on optimization of the fortran code.
I used the - vectorize option to compile for reducing the run time considerably and was happy. But... (1 Reply)
Discussion started by: schamarthi1
1 Replies
7. Programming
Hello everyone,
I'm trying since a few days to compile a f90 program with gfortran (on Ubuntu) with a makefile. The fortran program calls 2 routines written in C.
Here is my makefile:
FC = gfortran
SFC = gfortran
FFLAGS = -ffree-form -O... (21 Replies)
Discussion started by: leroygr
21 Replies
8. Programming
I have code that works fine in ifort. But when trying to run on gfortran 4.7.1 (which does support quads and has no problem with real * 16) I can't cast an integer variable to a quad precision float (real*16) using something like:
factq(i) = factq(i-1) * qfloat(i)
Finding a list of the new... (2 Replies)
Discussion started by: vibrantcascade
2 Replies
9. Programming
Hello
I am working on a CPP code written for SUN CC 5.5
and make
we used make to compile the code then it compilation went smooth
now i am using gmake:
I have a make file like this
WSROOT=..
include $(WSROOT)/etc/wsmkinclude.common
all:
@for subdir in */Makefile; \
do \... (1 Reply)
Discussion started by: Revathi R
1 Replies
10. Solaris
Hello
I am working on a CPP code written for SUN CC 5.5
and make
we used make to compile the code then it compilation went smooth
now i am using gmake:
I have a make file like this
WSROOT=..
include $(WSROOT)/etc/wsmkinclude.common
all:
@for subdir in */Makefile; \
do \... (1 Reply)
Discussion started by: Revathi R
1 Replies
LEARN ABOUT OSX
mailcap.order
MAILCAP.ORDER(5) Order Mailcap Entries MAILCAP.ORDER(5)
NAME
/etc/mailcap.order - the mailcap ordering specifications
DESCRIPTION
The order of entries in the /etc/mailcap file can be altered by editing the /etc/mailcap.order file. Each line of that file specifies a
package and an optional mime type. Mailcap entries that match will be placed in the order of this file. Entries that don't match will be
placed later.
Example
mime-support:*/*
gv:application/postscript
netscape:text/html
less:text/*
emacs:text/*
The above would make any entries provided by the mime-support package (as found in the /usr/lib/mime/packages directory) take priority over
everything else. The gv package will be used over anything else when it comes to postscript documents. Netscape will be used for any html
documents and less will be used for any remaining text documents. However, since neither netscape or less provide for editing documents,
any edit or compose actions will fall through to the emacs rules.
After modifying this file, be sure to run /usr/sbin/update-mime (as root) to propagate the changes into the /etc/mailcap file.
Remember that this files takes package names and not executable names. If you want to define rules that reference specific programs, the
best way is to include them in ~/.mailcap or the user section of the /etc/mailcap file.
LIMITATIONS
There is currently no way to break out a certain type from a wildcard rule. If, for example, both xv and gimp were to specify "image/*"
rules, it isn't possible to use xv for gif images but use gimp for jpeg images.
Also, I would like to add the ability to specify certain actions in the rules. For example, if netscape were to have an edit rule but I
wanted to use emacs for editing/creating html documents, I could place a line like
emacs:text/* action=edit|compose
before the netscape entry. The update-mime program would then spit out entries such that netscape view rule comes before the emacs view
rule but have the netscape edit rule comes after the emacs edit rule.
SEE ALSO
mailcap(5) run-mailcap(1) update-mime(8)
AUTHOR
The mailcap.order specification was written by Brian White <bcwhite@pobox.com>
Debian Project 16th Aug 1998 MAILCAP.ORDER(5)