>
>
> $hash{LIBS}[0] .= $^O =~ /MSWin/ ? '-L"C:/UT/LAPACK/lib/win32/" -lBLAS
> -lLAPACK -lMATGEN -lEXTRAS -L"C:/Program Files/Common Files/Intel/Shared
> Files/fortran/Lib/ia32" -lifcore -lmmd' : '';
>
> That should at least get you past those unresolved symbols that you
> reported. Whether it will get you past the additional fortran symbols that I
> came up against, I don't know. (And there may be similar problems with the
> Real and Complex stuff, too.) Anyway ... see how you go with that :-)
>
>
New unresolved symbols (this time intel fortran compilers')libifcore.lib(cvt_text_to_data.obj) : error LNK2001: unresolved external symbol__intel_fast_memset libifcore.lib(for_wseq.obj) : error LNK2019: unresolved external symbol __intel_ fast_memset referenced in function _for_write_seq .... libifcore.lib(for_m_qwin.obj) : error LNK2019: unresolved external symbol __f_ge ttextposition referenced in function __fq_gettextposition libifcore.lib(for_get.obj) : error LNK2019: unresolved external symbol __QWINRea d referenced in function _for__read_input. ..\blib\arch\auto\PDL\LinearAlgebra\Trans\Trans.dll : fatal error LNK1120: 43 un resolved externals Anyways im going to switch to Linux....hopefully that would ease out things. Jan mentioned the capability of using flags to cope with the changed names - > which would be better than rewriting the Trans.pd source as we have done. > But I know nothing about how to do that. > > Jan, what about the flags?? Cheers, Addy
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
