Compaq Visual Fortran 6.6 and Matlab r2009a
Nathan
that I can still use it? I don't want to go through the hassle of
buying a new compiler...
I'm on a 32-bit Windows XP system and want to use MEX with this
compiler.
Any help would be appreciated, as I've been searching for an hour to
no avail.
(I only ask if I can still use it because I saw a batch script that
allowed users to use an Intel Fortran Compiler with Matlab that is not
normally supported...)
TideMan
It's one reason that I haven't upgraded from Matlab 2006a - I can
still use CVF for MEX files.
Last year, I helped a colleague upgrade to Matlab 2008a and Intel. It
was a terrible performance. For a start, we needed to find a copy of
Visual Studio 2005. Then making all these programs talk to each other
took his IT people a couple of days before we even got to the Fortran
APIs. However, most of the CVF programs ported across to Intel
without problem once we got the system working. But it only works on
one PC, so that's the only one he can use for MEXing.
Anyway, a solution to your problem is to downgrade your version of
Matlab. I think the change to Intel occurred in version 2008a, so
anything before that will be OK.
IMHO, TMW have gone overboard with two new versions per year. Each
new version introduces more bugs and less stability, with a minuscule
enhancement of features.
Nathan
So downgrading is the only option? (Other than getting the Intel
compiler?)
Hm... I'll talk to my mentor and see what he wants to do.
I think it will be okay to just go ahead and get the intel, since I've
been reading that it's mostly compatible with CVF. Thanks for your
input. Matlab does seem to be updated way too quickly, I agree. More
bugs and compatibility issues should be fixed before moving on to
newer versions that mess up what you are working on. (The whole
phasing out process of previous compilers is also very troubling...
they are forcing us to keep older and possibly more buggy versions to
keep compatibility with trusted programs, or else we have to spend
more money on their products and "partner" products...)
Well, I'll be getting paid to figure out how to work with the intel
and matlab (if that's what we'll end up doing) so I don't mind the
trouble.
Again, thanks for the response.
Luka Djigas
wrote:
>
>Well, I'll be getting paid to figure out how to work with the intel
>and matlab (if that's what we'll end up doing) so I don't mind the
>trouble.
>
>Again, thanks for the response.
Shouldn't there be a compatibility table, of CVF, Intel compilers, ...
and Matlab's, somewhere on Matlab's site?
I can't find it now, but I know I saw it somewhere.
pp, Luka
Mark Westwood
I've not used CVF for a long time but I have some small experience of
getting Matlab to recognise unsupported compilers.
In a directory with a name like this:
C:\Program Files\MATLAB\R2009a\bin\win64\mexopts
you'll find a bunch of .bat and .stp files. All you have to do is
copy a suitable starting file (or two) and edit it (or them) to use
your compiler. You should be able to understand the contents and
layout of these files quite readily -- so I won't wear my fingers out
typing detailed instructions. Not sure I could anyway !
This will get you over one hurdle, getting Matlab to recognise that
your compiler exists when you do 'mex -setup'. Now, if there are
features of a Fortran compiler that Mex requires and that your version
of CVF doesn't provide, you're probably stuck.
Hope that helps
Mark Westwood
Nathan
Yeah, you're right.
I found this in the mexsetup file:
"Many .stp files are provided in <MATLAB>/bin/<ARCH>/mexopts and
<MATLAB>/bin/<ARCH>/mbuildopts. These can be used as examples for
creating
.stp files for other (non-MathWorks supported) compilers."
So I guess you are supposed to just go ahead and try to use your own
compilers? I'll try to figure out how to write one for CVF, I guess.
I'm not sure I understand the language in the batch files enough to
write one for CVF, however.
Thanks for your help!
-Nathan
dpb
>> In a directory with a name like this:
>>
>> C:\Program Files\MATLAB\R2009a\bin\win64\mexopts
>>
>> you'll find a bunch of .bat and .stp files. All you have to do is
>> copy a suitable starting file (or two) and edit it (or them) to use
>> your compiler. You should be able to understand the contents and
...
> Yeah, you're right.
> I found this in the mexsetup file:
> "Many .stp files are provided in <MATLAB>/bin/<ARCH>/mexopts and
> <MATLAB>/bin/<ARCH>/mbuildopts. These can be used as examples for
> creating .stp files for other (non-MathWorks supported) compilers."
> So I guess you are supposed to just go ahead and try to use your own
> compilers? I'll try to figure out how to write one for CVF, I guess.
> I'm not sure I understand the language in the batch files enough to
> write one for CVF, however.
> Thanks for your help!
> -Nathan
Yeah, I looked into it some a while back and got lost in the (what
seemed to me anyway) multiple levels of indirection pretty quickly.
I've not used mex in so long I don't recall whether CVF is supported w/
the version I have--I'll try to look and see what I can find if it is
that might be of any use.
--
Nathan
I've been working on this for about an hour, and can't seem to figure
out why it doesn't work (other than it's probably not supposed to
work).
Here's my "df66opts.bat" file information:
@echo off
rem DF66OPTS.BAT
rem
rem Compile and link options used for building MEX-files
rem using the Compaq Visual Fortran compiler version 6.6
rem
rem $Revision: 1.1 $ $Date: 2002/06/03 12:17:13 $
rem
rem
********************************************************************
rem General parameters
rem
********************************************************************
set MATLAB=%MATLAB%
set DF_ROOT=%DF_ROOT%
set VCDir=%DF_ROOT%\VC98
set MSDevDir=%DF_ROOT%\Common\msdev98
set DFDir=%DF_ROOT%\DF98
set PATH=%MSDevDir%\bin;%DFDir%\BIN;%VCDir%\BIN;%PATH%
set INCLUDE=%DFDir%\INCLUDE;%INCLUDE%
set LIB=%DFDir%\LIB;%VCDir%\LIB;%LIB%
rem
********************************************************************
rem Compiler parameters
rem
********************************************************************
set COMPILER=df
set COMPFLAGS=/fpp:"/m /S%MATLAB%/extern/include" /compile_only /
tune:host /nologo /DMATLAB_MEX_FILE /keep
set OPTIMFLAGS = /threads /optimize:4 /fast /arch:generic /
assume:nodummy_aliases /inline:speed
rem set OPTIMFLAGS=/libs:dll /threads /optimize:4 /fast /arch:generic /
assume:nodummy_aliases /inline:speed /DNDEBUG
set DEBUGFLAGS=/libs:dll /threads /dbglibs /debug:full /pdbfile
set NAME_OBJECT=/Fo
rem
********************************************************************
rem Linker parameters
rem
********************************************************************
set LIBLOC=%MATLAB%\extern\lib\win32\digital\df60
set LINKER=link
set LINKFLAGS=/DLL /EXPORT:_MEXFUNCTION@16 /LIBPATH:"%LIBLOC%"
libmx.lib libmex.lib libmat.lib /implib:%LIB_NAME%.lib /NOLOGO
set LINKOPTIMFLAGS=
set LINKDEBUGFLAGS=/debug
set LINK_FILE=
set LINK_LIB=
set NAME_OUTPUT="/out:%OUTDIR%%MEX_NAME%.dll"
set RSP_FILE_INDICATOR=@
rem
********************************************************************
rem Resource compiler parameters
rem
********************************************************************
set RC_COMPILER=rc /fo "%OUTDIR%mexversion.res"
set RC_LINKER=
And here's the "df66opts.stp" information:
# $Revision: 1.1.6.3 $ $Date: 2008/11/04 19:40:29 $
use mexutils;
sub intelf91msvs2005opts
{
#===================================================================
# df66opts: Define where the Compaq Visual Fortran
# compiler 6.6 is installed. Also sets language, version, and
# environment variables.
#===================================================================
my $input = shift;
# This is where the vendor installs the compiler by default
my $default_location = "C:\\Program Files\\Microsoft Visual Studios
\\DF98";
# Return language/technology this compiler compiles.
my @language_handled = ('FORTRAN');
# Find MSVC80
my $msvc80_record = callstpfile($input->{'matlab_bin'}."/
mexopts/","msvc80opts.stp");
my $msvc80_location_fcn = $msvc80_record->{"locate"};
my @msvc80_locations = &$msvc80_location_fcn;
my $msvc80_dir = pop @msvc80_locations;
my $locate_fcn = sub {
#===================================================================
# locate_fcn: A local function to return potential location
where this compiler
# is installed. The return value is used to set the
COMPILER_ROOT
# directory. It makes three guesses: The system path, the
registry, and
# the default location where the compiler tries to install
itself.
#===================================================================
my @df_roots = ();
my $registry_lookup_fcn = $input->{"registry_lookup"};
my $search_path_fcn = $input->{"search_path"};
# Search the default environment variable location.
$ifort_root = $ENV{'df66opts'};
if (-e "$df_root\\Bin\\df.exe"){
if (&correct_version("$df_root\\Bin\\df.exe","6.6")){
push(@df_roots, $df_root);
}
}
# Search the registry.
$df_root = &$registry_lookup_fcn("SOFTWARE\
\DigitalEquipmentCorporation\\VisualFortran\\6.6",
"VisualFortranPath");
# Verify it is the right version and strip part that is not
the ROOT.
# if (-e "$df_root\\Bin\\df.exe"){
# if (&correct_version("$dft_root\\Bin\\df.exe","6.6")){
# $df_root =~ s/\\6.6$//i;
# push(@df_roots, $df_root);
# }
# }
# Search the default install location.
# Verify it is the right version and strip part that is not
the ROOT.
if (-e $default_location . "\\Bin\\df.exe"){
if (&correct_version($default_location . "\\Bin\
\df.exe","6.6")){
push(@df_roots, $default_location);
}
}
return @df_roots;
};
my $root_val = sub {
my $base_directory = shift;
if (!$msvc80_dir){
my $errMsg="\nError: Microsoft Visual Studio 2005 was not
found by mex -setup.\n" .
" The Microsoft Visual Studio 2005
linker is required\n".
" to build Intel Fortran MEX-files.
Please make sure that\n".
" Microsoft Visual Studio 2005 is
installed properly.\n\n";
die $errMsg;
}
# Warn about upcoming deprecation of this compiler
print(mexDeprecationWarning("Intel Visual Fortran 9.1"));
return $base_directory;
};
return {
"vendor_name" => "Compaq Visual Fortran",
"version" => "6.6",
"group_id" => "COMPAQF",
"serial" => 6.0,
"root_var" => "df66opts",
"linker_var" => "VS80COMNTOOLS",
"optfile_name" => "df66opts.bat",
"linker_optfile_name" => "msvc80opts",
"default_location" => $default_location,
"language_handled" => \@language_handled,
"root_val" => $root_val,
"link_val" => $msvc80_dir,
"locate" => $locate_fcn,
};
}
1;
Am I missing something completely? Did I even edit these files
correctly?
All I get when typing mex -setup is:
Please choose your compiler for building external interface (MEX)
files:
Undefined subroutine &mexsetup::df66opts called at C:\PROGRA~1\MATLAB
\R2009a\bin\/mexsetup.pm line 444.
??? Error using ==> mex at 218
Unable to complete successfully.
Well, I just realized that I am missing something... the lib files
in ..\lib\win32\digital\df60
Because this compiler is no longer supported with Matlab, I don't get
those lib files (and also can't seem to find them anywhere online).
Does anybody know how to help me, or should I just move on and tell my
mentor to buy a newer (compatible) compiler?
Thanks
-Nathan
Nathan
Thanks, that'd be great. I think as long as I get the lib files I'm
missing (as well as the correct text inside the .stp and .bat files)
it should work...
-Nathan
dpb
...
> Thanks, that'd be great. I think as long as I get the lib files I'm
> missing (as well as the correct text inside the .stp and .bat files)
> it should work...
You're several rev's of ML later than I but I zipped up the df60 lib
files from here and sent them to your email addy. No clue whether
they'll work w/ a later version or not, but nothing ventured, nothing
gained. :J) Can't see there's much of a license issue TMW can complain
about since they pulled support as long as don't expect them to answer
questions or solve problems.
--
Nathan
Alright thanks. I'll post again after I try it out. By the way, does
the code I posted (that resides in df66opts.bat and df66opts.stp)
match the code in yours? These are/should be located in C:\program
files\matlab\(release)\bin\win32\mexopts
Another thing... does your folder also contain another batch file
named something like df66engmatopts.bat? I don't have that one (at
least I haven't tried creating it yet).
Thanks again for the lib files and your help.
-Nathan
dpb
...
> Alright thanks. I'll post again after I try it out. By the way, does
> the code I posted (that resides in df66opts.bat and df66opts.stp)
> match the code in yours? These are/should be located in C:\program
> files\matlab\(release)\bin\win32\mexopts
> Another thing... does your folder also contain another batch file
> named something like df66engmatopts.bat? I don't have that one (at
> least I haven't tried creating it yet).
I'll go look--my ML version is old enough it still has df60*.* instead
of 66 (altho I have 6.6c) so I thought I'd cut 'n paste yours but hadn't
yet done so...
I'll try to get to that here shortly--stay tuned... :)
--
Nathan
it is much appreciated.
I don't think there would be too much difference between the df60 and
df66 files, other than version numbers.
dpb
...
> Alright thanks. I'll post again after I try it out. By the way, does
> the code I posted (that resides in df66opts.bat and df66opts.stp)
> match the code in yours? These are/should be located in C:\program
> files\matlab\(release)\bin\win32\mexopts
The opts.bat file is pretty close except some of the compiler options
aren't quite the same -- one I noticed is the 6.6 version uses /threads
whereas my 6.0 doesn't.
The .stp file is quite markedly different -- the 6.0 version routine
name is df60opts while yours is intelf91msvs2005opts. The biggest
difference I see is a lot of stuff searching for MSVC80 and the
requirement for VS2005 that the 6.0 version doesn't have.
Whether you can get anywhere w/o them I don't know, nor do I yet know
whether I can manage to get 6.6c to work w/ my R12--I've intended to
look into it for years but when I (was) retired the incentive sorta'
went w/ it... :)
> Another thing... does your folder also contain another batch file
> named something like df66engmatopts.bat? I don't have that one (at
> least I haven't tried creating it yet).
This is for the building of standalone .exe's. Here's what mine looks
like fwiw (which may not be much)...
rem DF60ENGMATOPTS.BAT
rem
rem Compile and link options used for building standalone MAT programs
rem with DEC Fortran 6.0 compiler
rem
rem $Revision: 1.2 $ $Date: 2000/04/04 17:07:31 $
rem
rem ********************************************************************
rem General parameters
rem ********************************************************************
set MATLAB=%MATLAB%
set DF_ROOT=%DF_ROOT%
set
PATH=%DF_ROOT%\Common\msdev98\bin;%DF_ROOT%\DF98\BIN;%DF_ROOT%\VC98\BIN;%PAT
set INCLUDE=%DF_ROOT%\DF98\INCLUDE;%INCLUDE%
set LIB=%DF_ROOT%\DF98\LIB;%DF_ROOT%\VC98\LIB;%LIB%
rem ********************************************************************
rem Compiler parameters
rem ********************************************************************
set COMPILER=fl32
set OPTIMFLAGS=-Oxp -DNDEBUG
set DEBUGFLAGS=-Zi
set COMPFLAGS=-c -G5 -4R8 -nologo
set NAME_OBJECT=/Fo
rem ********************************************************************
rem Linker parameters
rem ********************************************************************
set LIBLOC=%MATLAB%\extern\lib\win32\digital\df60
set LINKER=link
set LINKFLAGS=/LIBPATH:"%LIBLOC%" libmx.lib libmat.lib libeng.lib
set LINKOPTIMFLAGS=
set LINKDEBUGFLAGS=/debug
set LINK_FILE=
set LINK_LIB=
set NAME_OUTPUT="/out:%OUTDIR%%MEX_NAME%.exe"
set RSP_FILE_INDICATOR=@
rem ********************************************************************
rem Resource compiler parameters
rem ********************************************************************
set RC_COMPILER=
set RC_LINKER=
dpb
...
> Hm. I haven't received the lib files yet. But thanks for your support,
> it is much appreciated.
Well, I have an explanation for that; just arrived. gmail bounced it
for the executable attachment, apparently. You have another address?
> I don't think there would be too much difference between the df60 and
> df66 files, other than version numbers.
The problem(s) I foresee will be less in the DVF end than in what TMW
has done to the interfaces inside ML from the different versions of ML
between us. I mentioned there's a major difference between the two .stp
files in another response. But, it wasn't/isn't clear to me from what
you started.
--
Nathan
Ah, alright.
The difference between the .stp files was due to me trying to piece
the CVF one together from an intel version...
But hey, I solved my problem! I installed r2007b, copied the
required .bat and .stp files over from \bin\win32\mexopts
And I guess I did have the lib files, but was pointing to the wrong
area (They are in the microsoft folder under extern\lib)
Thanks for your help, however.
Here's the real .bat and .stp files for you, if you want to try to
make it work with 6.6.
(cvf66engmatopts.bat)
@echo off
rem CVF66ENGMATOPTS.BAT
rem
rem Compile and link options used for building stand-alone engine
or MAT
rem programs with Compaq Visual Fortran compiler version 6.6.
rem
rem $Revision: 1.1.8.2 $ $Date: 2006/06/23 19:04:33 $
rem
rem
********************************************************************
rem General parameters
rem
********************************************************************
set MATLAB=%MATLAB%
set DF_ROOT=%DF_ROOT%
set PATH=%DF_ROOT%\Common\msdev98\bin;%DF_ROOT%\DF98\BIN;%DF_ROOT%
\VC98\BIN;%PATH%
set INCLUDE=%DF_ROOT%\DF98\INCLUDE;%INCLUDE%
set LIB=%DF_ROOT%\DF98\LIB;%DF_ROOT%\VC98\LIB;%LIB%
set MW_TARGET_ARCH=win32
rem
********************************************************************
rem Compiler parameters
rem
********************************************************************
set COMPILER=df
set COMPFLAGS=/fpp:"/m /S%MATLAB%/extern/include" /c /G5 /4R8 /nologo /
fixed
set OPTIMFLAGS=/Oxp /DNDEBUG
set DEBUGFLAGS=/Zi
set NAME_OBJECT=/Fo
rem
********************************************************************
rem Linker parameters
rem
********************************************************************
set LIBLOC=%MATLAB%\extern\lib\win32\microsoft
set LINKER=link
set LINKFLAGS=/LIBPATH:"%LIBLOC%" libmx.lib libmat.lib libeng.lib /
nologo
set LINKOPTIMFLAGS=
set LINKDEBUGFLAGS=/debug
set LINK_FILE=
set LINK_LIB=
set NAME_OUTPUT="/out:%OUTDIR%%MEX_NAME%.exe"
set RSP_FILE_INDICATOR=@
rem
********************************************************************
rem Resource compiler parameters
rem
********************************************************************
set RC_COMPILER=
set RC_LINKER=
(cvf66opts.bat)
@echo off
rem CVF66OPTS.BAT
rem
rem Compile and link options used for building MEX-files
rem using the Compaq Visual Fortran compiler version 6.6
rem
rem $Revision $ $Date: 2006/06/23 19:04:34 $
rem
rem
********************************************************************
rem General parameters
rem
********************************************************************
set MATLAB=%MATLAB%
set DF_ROOT=%DF_ROOT%
set VCDir=%DF_ROOT%\VC98
set MSDevDir=%DF_ROOT%\Common\msdev98
set DFDir=%DF_ROOT%\DF98
set PATH=%MSDevDir%\bin;%DFDir%\BIN;%VCDir%\BIN;%PATH%
set INCLUDE=%DFDir%\INCLUDE;%INCLUDE%
set LIB=%DFDir%\LIB;%VCDir%\LIB;%LIB%
set MW_TARGET_ARCH=win32
rem
********************************************************************
rem Compiler parameters
rem
********************************************************************
set COMPILER=df
set COMPFLAGS=/fpp:"/m /S%MATLAB%/extern/include" -c -nokeep -G5 -
nologo -DMATLAB_MEX_FILE /fixed
set OPTIMFLAGS=/MD -Ox -DNDEBUG
set DEBUGFLAGS=/MD -Zi
set NAME_OBJECT=/Fo
rem
********************************************************************
rem Linker parameters
rem
********************************************************************
set LIBLOC=%MATLAB%\extern\lib\win32\microsoft
set LINKER=link
set LINKFLAGS=/DLL /EXPORT:_MEXFUNCTION@16 /MAP /LIBPATH:"%LIBLOC%"
libmx.lib libmex.lib libmat.lib /implib:%LIB_NAME%.lib /NOLOGO
set LINKOPTIMFLAGS=
set LINKDEBUGFLAGS=/debug
set LINK_FILE=
set LINK_LIB=
set NAME_OUTPUT="/out:%OUTDIR%%MEX_NAME%%MEX_EXT%"
set RSP_FILE_INDICATOR=@
rem
********************************************************************
rem Resource compiler parameters
rem
********************************************************************
set RC_COMPILER=rc /fo "%OUTDIR%mexversion.res"
set RC_LINKER=
set POSTLINK_CMDS=del "%OUTDIR%%MEX_NAME%.map"
(cvf66opts.stp)
# $Revision $
sub cvf66opts
{
my $input = shift;
my $default_location = "C:\\Program Files\\Microsoft Visual
Studio";
my @language_handled = ('FORTRAN');
my $locate_fcn = sub {
my @df_roots = ();
my $registry_lookup_fcn = $input->{"registry_lookup"};
my $search_path_fcn = $input->{"search_path"};
my $df_root = &$search_path_fcn("fl32.exe");
if ($df_root =~ /\\df98\\bin$/i)
{
$version=`\"$df_root\\fl32.exe\"`;
if ($version =~ /Version 6.6/)
{
$df_root =~ s/\\df98\\bin$//i;
push(@df_roots, $df_root);
}
}
$df_root = &$registry_lookup_fcn("SOFTWARE\
\DigitalEquipmentCorporation\\VisualFortran\\6.6",
"DevStudioPath");
if (-e "$df_root")
{
$df_root =~ s/\\Common$//i;
push(@df_roots, $df_root);
}
if (-e "$default_location\\DF98\\BIN")
{
$version=`\"$default_location\\DF98\\BIN\\fl32.exe\"`;
if ($version =~ /Version 6.6/)
{
push(@df_roots, $default_location);
}
}
return @df_roots;
};
my $root_val = sub {
print
"\n***************************************************************************
\n" .
" Warning: The Compaq Visual Fortran 6.6 compiler is
being phased out and \n" .
" will not be supported in a future release.
\n" .
" For a list of currently supported compilers
see: \n" .
" http://www.mathworks.com/support/tech-notes/1600/1601.html\n"
.
"***************************************************************************
\n";
return shift;
};
return {
"vendor_name" => "Compaq Visual Fortran",
"version" => "6.6",
"group_id" => "DVF",
"serial" => 3.0,
"root_var" => "DF_ROOT",
"optfile_name" => "cvf66opts.bat",
"default_location" => $default_location,
"language_handled" => \@language_handled,
"root_val" => $root_val,
"locate" => $locate_fcn,
"post_setup_hook" => $post_setup_hook
};
}
1;
Another thing... If you're using a version before r2007a, the mex-file
extensions have changed. They used to be just .dll files, but now they
are .mexw32 (for windows 32 bit system) and the like.
Again, thanks for the help. It looks like I wont be needing those .lib
files anyways!
(And note: when you want to email a zip file with executables, just
rename the zip file to exclude the extension and tell the person you
are sending it to that they just need to add the extension)
Luka Djigas
wrote:
>(And note: when you want to email a zip file with executables, just
>rename the zip file to exclude the extension and tell the person you
>are sending it to that they just need to add the extension)
RAR it, @gmail doesn't check inside of those.
pp, Luka
dpb
...
> But hey, I solved my problem! I installed r2007b, copied the
> required .bat and .stp files over from \bin\win32\mexopts
That's kewl, glad to know.
I'm stuck w/
mex -setup
only returning CVF 6.0 as a version even though it's been upgraded to 6.6c.
You have any idea w/o wasting further time how ML tries to ascertain the
version? I know recall where I was when I got stuck previously--this
point where it didn't seem to be able to tell which compiler was
installed even. I looked at the setup.m file but it calls a Perl script
and I got lost at that point... :(
--
Nathan
Ah, sorry. I don't know how to help you if creating those files in the
right folder didn't work. (Once I copied them into the corresponding
r2009a folder, mex -setup finally gave it as an option)
Good luck! Inside of each of these files, they specify which version
the compiler (for those files) is used. The .stp file more explicitly
declares that with a variable that holds the version number. Without
any more information, I don't think I'd be able to help.
However, I do appreciate you taking your time to help me with my prior
problem!
-Nathan