%% Nils Wedi <[EMAIL PROTECTED]> writes:
nw> thanks very much for your reply. I am sorry I did not send you the
nw> correct dependencies that were used on each machine.It seems
nw> infact that gmake is *NOT* case sensitive.
I don't know what you're trying to say, but GNU make (on UNIX systems)
_is_ absolutely case sensitive. There is no question about it.
nw> However, this is problematic since the filenames of the result do
nw> not correspond and if like in our case we sometimes want to use
nw> pre-compiled modules (which have uppercase names). So for gmake to
nw> work with appropriate time-stamps we would need to make always two
nw> versions of the modules, an uppercase one for the compiler and a
nw> lowercase one for gmake. The other option, since I can't seem to
nw> tell the compiler to create lowercase modules, would be to change
nw> gmake to understand uppercase rules, is there an option or switch
nw> that I need to put ?
There is a compile option you can use and rebuild make; add a line like:
#define HAVE_CASE_INSENSITIVE_FS
to your config.h file after running configure.
This option is never tested on UNIX (it's used by some of the ports) so
I can't say how well it will work.
Your other option is to change the rule that generates the .mod file so
that it renames the file to be lowercase. So you have a rule like this:
%.o %.mod : %.F90
...
@mv `echo $* | tr a-z A-Z`.mod $*.mod
Now even though the compiler generates the file as FOO.mod, the make
rule will rename it to foo.mod.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://make.paulandlesley.org
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
_______________________________________________
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make
