RE: VC 8 and 64-bit ActivePerl
On Wed, 06 May 2009, Sisyphus wrote: Jan Dubois j...@activestate.com wrote: Either that, or you could embed the manifest manually into your Common.dll using the mt.exe tool. Thanks Jan. I've taken a look at 'mt /?' and can't see anything there that makes any sense at all to me. Do you know the actual command I need to run ? It would be something like this: mt -nologo -manifest Common.dll.manifest -outputresource:Common.dll;2 There's no 'manifest' file anywhere in the build directory (apart from the MANIFEST that ships with the XML-LibXML-Common source). I've tried updating to EU::MM-6.50, but that makes no difference. The *.manifest file gets written by link.exe when it builds the DLL using VC 8. It should be in the same directory as the *.dll. You need to call mt.exe after link.exe. Cheers, -Jan ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: VC 8 and 64-bit ActivePerl
- Original Message - From: Jan Dubois j...@activestate.com Do you know the actual command I need to run ? It would be something like this: mt -nologo -manifest Common.dll.manifest -outputresource:Common.dll;2 The *.manifest file gets written by link.exe when it builds the DLL using VC 8. It should be in the same directory as the *.dll. You need to call mt.exe after link.exe. I can see that the Makefile actually runs that command after link.exe: if exist blib\arch\auto\XML\LibXML\Common\Common.dll.manifest mt -nologo -manifest blib\arch\auto\XML\LibXML\Common\Common.dll.manifest -outputresource: blib\arch\auto\XML\LibXML\Common\Common.dll;2 But 'blib\arch\auto\XML\LibXML\Common\Common.dll.manifest' does not exist. Note that I'm not actually building XML-LibXML-Common with VC 8. I'm using the Platform SDK, Windows Server 2003 R2 compiler. It's just that I'm linking against dynamic xml2 and iconv libraries that were built with VC 8. It all works fine, except for the runtime error. (There must surely be a way of resolving this without having to build the libraries using the SDK compiler.) I did find a manifest file for an x86 Net::SSH2 dll, and I've tried to create a manifest file for Common.dll based on it. But I don't seem to be able to get it right. With my Common.dll.manifest file in place, I can then successfully run the mt.exe command, but 'nmake test' then outputs the error: Can't load 'blib\arch/auto/XML/LibXML/Common/Common.dll' for module XML::LibXML: :Common: load_file:The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail at C:/_64/perl1004/lib/DynaLoader.pm line 202. at test.pl line 10 Cheers, Rob ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: Win32::ODBC
Yes. The sql works fine against the DB directly. It's a stored procedure with output variables. I can run the contents of the stored proc within my perl code, but not the proc itself. I'm wondering if it's a driver issue. Peter W Schwartz Vice-President IB Technology - Prime Brokerage / JP Morgan Chase (973) 793-7407 _ From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Paul Rogers Sent: Wednesday, May 06, 2009 9:18 PM To: perl-win32-users@listserv.ActiveState.com Subject: RE: Win32::ODBC Have you attempted to execute this SQL code in DB2 prior? In other words skip the perl middleman altogether and see if it's something with your SQL statement. Paul --- From: perl-win32-users-boun...@listserv.activestate.com [mailto:perl-win32-users-boun...@listserv.activestate.com] On Behalf Of Schwartz, Peter (JPMC) Sent: Wednesday, May 06, 2009 5:45 PM To: Paul Rogers; perl-win32-users@listserv.ActiveState.com Subject: RE: Win32::ODBC Nope. The results are the same error. Could it have to do with the stored procedure having output variables? Peter W Schwartz Vice-President IB Technology - Prime Brokerage / JP Morgan Chase This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email. ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Net::SSLeay on Windows X64
We're running Activestate Perl 5.10.0.1004 on Windows x64. We are interested in the Net::SSLeay package for x64, but we have not had success locating a PPM that works, nor success build it using the free compilers/linkers available. Anyone know of a Net::SSLeay PPM distribution that works on Windows X64, or has anyone had success building one? Thanks! --- Gerry O'Brennan Systems Administrator Missouri University of Science and Technology 104 Computer Science, 1870 Miner Circle Dr. Rolla, Missouri 65409-0360 image001.png___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
RE: VC 8 and 64-bit ActivePerl
On Thu, 07 May 2009, Sisyphus wrote: From: Jan Dubois j...@activestate.com Note that I'm not actually building XML-LibXML-Common with VC 8. I'm using the Platform SDK, Windows Server 2003 R2 compiler. It's just that I'm linking against dynamic xml2 and iconv libraries that were built with VC 8. Are you sure you are dynamically linking against xml2 and iconv libraries? In that case there would be no need for your DLL to contain the manifest; only the xml2 and iconv2 libraries themselves would have to embed it. I suspect that you are statically linking against some code that has been compiled with VC8, so you'll have a direct reference to MSVCR80.dll in you DLL. You can check with depends.exe, dumpbin.exe, or simply link /dump /imports Common.dll to see which external references you have. If you have a reference to MSVCR80.dll then you did statically link some VC8 generated code. It all works fine, except for the runtime error. (There must surely be a way of resolving this without having to build the libraries using the SDK compiler.) I did find a manifest file for an x86 Net::SSH2 dll, and I've tried to create a manifest file for Common.dll based on it. But I don't seem to be able to get it right. With my Common.dll.manifest file in place, I can then successfully run the mt.exe command, but 'nmake test' then outputs the error: Can't load 'blib\arch/auto/XML/LibXML/Common/Common.dll' for module XML::LibXML: :Common: load_file:The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail at C:/_64/perl1004/lib/DynaLoader.pm line 202. at test.pl line 10 The minimum change for the Manifest would be to change the architecture from x86 to amd64, but it is possible that the assembly version number of MSVCR80.dll needs to be adjusted as well. This is the main point of having the manifest in the first place that you can select a specific version of MSVCR80.dll from the assembly cache even if multiple versions are installed side-by-side in %WINDIR%\\WinSxS. Cheers, -Jan ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: VC 8 and 64-bit ActivePerl
- Original Message - From: Jan Dubois j...@activestate.com To: 'Sisyphus' sisyph...@optusnet.com.au; perl-win32-users@listserv.ActiveState.com Sent: Friday, May 08, 2009 2:39 AM Subject: RE: VC 8 and 64-bit ActivePerl On Thu, 07 May 2009, Sisyphus wrote: From: Jan Dubois j...@activestate.com Are you sure you are dynamically linking against xml2 and iconv libraries? Yes - if either msvcr80.dll, libxml2.dll, or libiconv.dll cannot be found, I get a pop-up telling me so. In that case there would be no need for your DLL to contain the manifest; only the xml2 and iconv2 libraries themselves would have to embed it. Bingo - that's it !! Hidden away in the lib folder of this pre-compiled package I found a libxml2.dll.manifest, which I then embedded into the libxml2.dll using mt.exe - and 'nmake test' now succeeds, passing all tests. There was no manifest for the iconv dll, but apparently it doesn't need it. (Perhaps the manifest is already embedded in it.) Thanks again, Jan. Cheers, Rob ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Re: Net::SSLeay on Windows X64
- Original Message - From: OBrennan, Gerry obren...@mst.edu To: perl-win32-users@listserv.ActiveState.com Sent: Thursday, May 07, 2009 11:49 PM Subject: Net::SSLeay on Windows X64 We're running Activestate Perl 5.10.0.1004 on Windows x64. We are interested in the Net::SSLeay package for x64, but we have not had success locating a PPM that works, nor success build it using the free compilers/linkers available. Do you have the compiler that built ActivePerl 5.10.0.1004 for Windows x64 ? It's called Windows Server 2003 R2 Platform SDK and you can get it at at: http://www.microsoft.com/downloads/details.aspx?familyid=484269E2-3B89-47E3-8EB7-1F2BE6D7123Adisplaylang=en You can get an x64 build of openssl (that was built using VC 8) from http://pecl2.php.net/downloads/php-windows-builds/php-libs/VC8/x64/ I grabbed http://pecl2.php.net/downloads/php-windows-builds/php-libs/VC8/x64/openssl-0.9.8h-vc8-x64.zip and have just used my Windows Server 2003 R2 Platform SDK compiler to build Net-SSLeay-1.35 against that VC 8 build of openssl. (I have the same build of perl as you, btw.) One test failed (t/local/00_ptr_cast.t), but it fails only because it fails to compile a test program: fatal error C1083: Cannot open compiler generated file: 'ptr_cast_test.obj': Permission denied Not sure why that error occurs - I'll have to play around with it. All other tests pass. If you don't want to mess around trying to build Net-SSLeay-1.35 yourself, I could send you a ppm package of it - just let me know. I've never used ppm with my x64 build of perl ... I assume it works fine with the x64 builds. Cheers, Rob ___ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
