Did you build your copy of perl with Borland? If not, then you probably on a hiding to nothing.
Whilst DLLs ought to be independant of the compilers that produce them, my experience is that the DLLs produced when building perl extensions seem to have some peculiar dependancies that often make it impossible to use one built with Borland in conjuction with a perl built with VC++ (ie. AS).
I've not really tied down quite why this is the case, I did spend some time trying to investigate it, but got kind of demoralised and gave up. I have built some modules with Borland that result in a dll that work fine with AS, but mostly not.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.
| [reply] |
Thanks for the advise. :-)
I will try to look for a visual C compiler to compile the DLL with. Making it to compile with borland was a bit hard.
| [reply] |
Unfortunately, that tends to be the case, which is a crying shame. It rankles with me that the only way to use Perl on the Win32 platform forces so many people into either purchasing VC++ (and throwing good money into the MS coffers!) or obtaining it through "dubious means", when there are several free compilers available.
There is the Cygwin route of course, but that adds yet another unnecessary and complicating layer into the mix.
Unless we could build up a head of steam behind one, free, native Win32 compiler, the situation of dependancy upon VC++ will continue:(
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.
| [reply] |
crazyinsomniac plays with Sybase and has the compiled driver in his PPM repository. If that is not what you need he could be a good person to ask....
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
| [reply] |
Hi Tachyon, yes I have ppm installed his compiled DBD::Sybase from his PPM repository. But that version was giving the same error messages too.
| [reply] |
AS build with cl.exe (part of M$ Visual C++ these days)and things work so much easier if you go with the flow. If you are/know a student you can get it for next to nothing. Anyway, I can't compile the driver for you as you need the Sybase headers on the system to do it and I don't have them. Hopefully someone will have.
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
| [reply] |
Oh really?
Did you do like
install_sybase says?
I suggest you do ;)
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | | ** The third rule of perl club is a statement of fact: pod is sexy. |
| [reply] |
Just like BrowserUK says, you proably need to build the module in exactly the same environment as your Perl was built.
But, whatever the case, a very good place to ask these questions is on the dbi-users@perl.org mailing list. You can find details at http://dbi.perl.org
jdtoronto | [reply] |