From: Anthony on
I had the exact same problem and I could not do anything to fix it despite spending hours over the past few days. I tried with both the VS2005 and VS2008 compilers. I have a 64-bit vista platform as well, I'm wondering if that may be related to the problem? Have you had any luck fixing it?
From: Keerthi Kamal on
"Anthony " <aerlinger(a)gmail.com> wrote in message <hbog75$gn2$1(a)fred.mathworks.com>...
> I had the exact same problem and I could not do anything to fix it despite spending hours over the past few days. I tried with both the VS2005 and VS2008 compilers. I have a 64-bit vista platform as well, I'm wondering if that may be related to the problem? Have you had any luck fixing it?

I do have the exact problem, Im running vista 64 bit, matlab r2008b 64 bit, vs2008 on a mac book pro with 9400M graphics card.
From: Keerthi Kamal on
"Anthony " <aerlinger(a)gmail.com> wrote in message <hbog75$gn2$1(a)fred.mathworks.com>...
> I had the exact same problem and I could not do anything to fix it despite spending hours over the past few days. I tried with both the VS2005 and VS2008 compilers. I have a 64-bit vista platform as well, I'm wondering if that may be related to the problem? Have you had any luck fixing it?

I fixed the problem, I went thorugh this page
http://julianapena.com/2009/09/how-to-install-and-configure-cuda-on-windows/
it says cuda 2.3 is not perfected for notebooks, so i installed cuda 2.2 toolkit. It runs fine.
From: Thomas on
Hi,
same problem for me.
I've got Windows7 64 bit, Matlab2008b, Cuda2.3 and I'm getting the same 6 unresolved externals.

"Oliver Woodford" <o.j.woodford.98(a)cantab.net> wrote in message <h9sm4g$ihm$1(a)fred.mathworks.com>...
> "mklcst Costola" wrote:
> >
> > I get this error:
> >
> > Note that only Visual Studio compilers are supported.
> > Creating cudamexopts.bat based on mexopts.bat...
> > Creating cuda_mex.pl based on mex.pl...
> > ??? Error using ==> fprintf
> > Invalid file identifier. Use fopen to generate a valid file identifier.
> >
> > Error in ==> setup_cuda_mex at 73
> > fprintf(fid_cuda_mex, '%s', line);

This is because you're not allowed to write to $matlabroot/bin/
I got the same error, so I created the file somewhere else and moved it there as administrator.
Unfortunately, I couldn't compile the example:
>> cuda_mex example.cu
WARNING: $ARCH (UNKNOWN) not set correctly [win64]

C:\PROGRA~1\MATLAB\R2008B\BIN\CUDA_MEX.PL:
Error: Using options file:
C:\Users\tom\AppData\Roaming\MathWorks\MATLAB\R2008b\cudamexopts.bat
You cannot use this file with the UNKNOWN architecture because it enables
a compiler for a different architecture.
Running mex -setup may resolve this problem.

??? Error using ==> cuda_mex at 213
Unable to complete successfully.

It doesn't seem to like the -win64 option passed to cuda_mex.pl

I then tried compiling the example with the nvmex.m / nvmex.pl combination that came with the MATLAB_CUDA_1.1 package but that wouldn't work either:
nvmex -f nvmexopts.bat example.cu -I"C:\Program Files\CUDA\include" -L"C:\Program Files\CUDA\lib" -lcufft -lcudart
Undefined subroutine &main::uuidgen called at C:\Program Files\MATLAB\R2008b\bin\nvmex.pl line 728.
??? Error using ==> nvmex at 206
Unable to complete successfully.

So I installed http://search.cpan.org/~caugustin/UUID-Tiny-1.02/lib/UUID/Tiny.pm to C:\Program Files\MATLAB\R2008b\sys\perl\win32\lib\UUID\, included a 'use UUID::Tiny;' at the top of nvmex.pl, added the following line above line 728:
my $uuid = create_UUID_as_string(UUID_V1);
and replaced uuidgen() with $uuid
This got me to the next error:
>> nvmex -f nvmexopts.bat example.cu -I"C:\Program Files\CUDA\include" -L"C:\Program Files\CUDA\lib" -lcufft -lcudart
uuid: 2e701816-d000-11de-82de-cbe830d9e0fc
WARNING: $ARCH (UNKNOWN) not set correctly [win64]

C:\PROGRA~1\MATLAB\R2008B\BIN\NVMEX.PL:
Error: Using options file:
nvmexopts.bat
You cannot use this file with the UNKNOWN architecture because it enables
a compiler for a different architecture.
Choose a file that is compatible with the UNKNOWN architecture.

??? Error using ==> nvmex at 206
Unable to complete successfully.

Which is where I gave up.

Any comments, thoughts or suggestions how to fix this mess?
Tom
From: dsss on
On Nov 12, 5:01 pm, "Thomas " <tgutz...(a)ee.uwa.edu.au> wrote:
> Hi,
>
> Any comments, thoughts or suggestions how to fix this mess?
> Tom

Use CUDA 2.2, not 2.3. I had similar problems, but now I can compile
the fft2_cuda.c routines... just not the .cu "accelerated" files
yet...I still have issues with the nvmex.pl command