| From: | "CAMPBELL, BRIAN D (BRIAN)" <campbelb [...] lucent.com> |
| To: | "CAMPBELL, BRIAN D (BRIAN)" <campbelb [...] lucent.com>, Jonathan Leffler <jleffler [...] us.ibm.com> |
| CC: | "'bug-DBD-Informix [...] rt.cpan.org'" <bug-DBD-Informix [...] rt.cpan.org>, dbd.informix [...] gmail.com |
| Subject: | RE: ANNOUNCE: IBM Informix Database Driver for Perl DBI Version 2 005.02 (2005-07-29) released |
| Date: | Fri, 2 Sep 2005 18:10:32 -0500 |
Jonathan,
I presume that you've had about 3 weeks now to digest this message.
What is the game plan? Do you plan to include some or all of these solutions in future versions of DBD::Informix?
Did you expect further involvement by me? Specifically, did you want or need me to help develop source code changes for any of my recommended solutions? I'm referring to those problems where I did not implement the recommended solution, but I used a workaround instead -- which is most of them.
Show quoted text
-----Original Message-----
From: CAMPBELL, BRIAN D (BRIAN) [mailto:campbelb@lucent.com]
Sent: Thursday, August 11, 2005 11:12 AM
To: Jonathan Leffler; dbi-users@perl.org
Cc: 'bug-DBD-Informix@rt.cpan.org'; dbd.informix@gmail.com
Subject: RE: ANNOUNCE: IBM Informix Database Driver for Perl DBI Version
2 005.02 (2005-07-29) released
My huge reply to this thread (which is a problem/solution report) appears below the ==== separator line. If you found this email posting to be
Helpful, please drop me an email.
- Brian
________________________________________
From: Jonathan Leffler [mailto:jonathan.leffler@gmail.com]
Sent: Wednesday, August 10, 2005 4:53 PM
To: CAMPBELL, BRIAN D (BRIAN)
Cc: DBI Users Mailing List
Subject: Re: Informix DBD build on Windows - Better
-----Original Message-----
On 8/8/05, CAMPBELL, BRIAN D (BRIAN) <campbelb@lucent.com> wrote:
All in all I uncovered 9 bugs in the build process for DBD.
Should I go ahead and publish my findings to this mailing list (DBI
users)?
As Ron said ("Publish and Be Damned")
Yes - please post bug reports - preferably with the patches to fix them - to the list. They may help other people; eventually, they'll help me help you.
As discussed wholly separately, t08fork.t failures indicate problems in the test, and t91udts.t failures indicate that the database wasn't as clean as it should be (arguably a test problem in itself). Not dreadfully significant, though both should ideally be fixed.
-----Original Message-----
From: CAMPBELL, BRIAN D (BRIAN) [mailto:campbelb@lucent.com]
Sent: Wednesday, August 03, 2005 4:42 PM
To: 'dbi-users@perl.org'
I tried building the recently released Informix DBD 2005.02 today. I apparently have a successful compile and link. But I'm having a major problem on the test. Below is the link input and output, and the first test. All remaining tests look like the first test. Help and suggestions needed. Here's the message I'm getting upon running the first test (and all the rest).
Can't find 'boot_DBD__Informix' symbol in ./Informix.dll
[stuff snipped]
My Environment:
* Windows 2000 [Version 5.00.2195] SP4
* ActiveState Perl v5.8.7 built for MSWin32-x86-multi-thread, Binary build 813 [148120]
* DBI: 1.48
* ESQL: IBM Informix CSDK Version 2.90, IBM Informix-ESQL Version 2.90.TC1
* Microsoft Visual C++ 6.0
* Connection to Informix DB server 9.21.FC4 on an Alpha box running Compaq Tru64 Unix.
========================================================================
This posting documents the problems I had while trying to build the recently
released Informix DBD 2005.02 on Windows.
First of all, the makefile generator produces this notice for Windows systems:
This is a semi-experimental version of Makefile.PL with Win32 (NT)
support. Previous versions have been tested on NT, but there could
still be bugs in this code. Please help save the world by trying
to debug the NT code and reporting the results back to the DBI
Users mailing list.
So once again, here I go, saving the world...
In the documetation below, I use the following "pattern language" for
each problem:
The symptom - the message from the console.
The reason - my best guess on what is causing the symptom.
A workaround (sometimes) - I provided an expediant "Workaround", which
I used to keep going.
A recommended solution - Usually just a description and nothing as fancy
as a real patch.
A preliminary remark: I recently upgraded my Perl to 5.8.7. In doing so,
I took my own previous advice and installed it in "C:\Perl" which I believe
is the default path provided by the ActiveState installer. Previously,
it was installed in "C:\Program Files\Perl", per a local site installation
process. Having that blank char in the Perl path caused all kinds of grief
in previous build attempts, as well documented in my previous post on the
subject:
http://www.mail-archive.com/dbi-users@perl.org/msg19771.html
The majority of problems I encountered then had that one root cause.
The build process uses several Perl modules to due some preliminary set
up; these modules were not good at handling spaces in file paths.
Thus, I was able to avoid a class of problems I had encountered previously.
It was also helpful to use my Batch file tip and CPAN/Config.pm tip as
described near the bottom of that posting.
OK, now on to the problem set...
[ 9 problems snipped ]
Message body not shown because it is not plain text.