Local compiler configuration?

[Neil_Carlson]

I have a remote collaborator who is experiencing inexplicable errors with my code that I am completely unable to reproduce. We are on nearly identical platforms and are compiling with 14.0.2 with exactly the same flags (and running the same test problem).  Grasping at straws, I'm wondering if the compiler installation provides for some local "configuration" file that allows the compiler to be configured differently than a stock installation, and if so, how I could tell.  I ask because I've just discovered apparent differences in the format of an unformatted file: the initial 4-byte record header is '00 00 00 08' (hexdump) where I am expecting '08 00 00 00' -- it's as if some sort of byte swapping option is being used. 

[IanH]

There's ifort.cfg in the installation hierarchy.  A user can specify a local version with the IFORTCFG environment variable.

I would be having a very close look at other environment variables that affect the compile time and runtime behaviour of the compiler and its generated programs too, for example FORT_CONVERTxxx.