Tim,
> > On Mon, Feb 23, 2004 at 08:47:44AM -0500, Rafael Caceres wrote: > > > Bjorn: > > > > > > No, I abandoned the idea after reading several postings indicating > > that > > > there were problems with 64 bit perl. > > > > Can you be more specific? Which version of perl, for example. > > > > Tim. > > The following recomendation comes to mind.. > -----Original Message----- > From: Alan Burlison [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 14, 2003 4:13 AM > To: Richard Felkins > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: DBD::Oracle - wrong ELF class: ELFCLASS64 > > > Richard Felkins wrote: > > > The compiler is the latest version from Sun as Forte or > > I guess it is SunOne now. I had tried to build a 5.8 > > 64 bit Perl a few months back and ran into serious make > > problems and abandoned that idea. I have checked and > > have the sparcv9 version of ld in the path. This Oracle > > is patched to 9.2.0.3.0 currently. > > 64-bit perl does build OK, but unless you need huge (>4Gb) amounts of > data, > I'd recommend you avoid it. > > > I have mixed feelings about forcing it to use the 32 bit > > library set. I'll try this as a last resort work around. > > We are building customer deliverables and need this process > > to be repeatable with documentation on the next CPAN upgrade. > > You won't *ever* get it to link unless you do. I know a patch was > submitted > > for this a while back, and I'm sure Tim has something in the works. > If your > > perl is 32-bit (and as I said I recommend that it is) you will need to > link > against the 32-bit Oracle libraries. There should be absolutely *no* > issue > with running a 32-bit client (e.g. DBD::Oracle) against a 64-bit > Database > server. > > -- > Alan Burlison > -- Regards, Rafael Caceres
