Re: DBD::Informix Installation on Sun Solaris 2.8 Problem

Andrew Hamm wrote: > Jonathan Leffler wrote: > >>>Testing whether your Informix test environment will work... >>>gcc: language arch=v9 not recognized >> >>You have a GCC - it is complaining about the Sun C options. Is your >>Perl a 64-bit version? If not, you'll have problems with CSDK >>2.81.FC2 (ESQL/C 9.53.FC2) because the ESQL/C library assumes a 64-bit >>environment. You'd need to use 'gcc -m64' -- if it complains about > > > I had exactly this experience a few weeks ago, and had to temporarily > install a 32 bit engine, CSDK and do a build; since I've not built 64 bit > Perl yet, and it was my first time on Solaris (smokes cigarette). Well, you didn't have to install the 32-bit server; you could have used either oltlitcp or olipcstr connections from the 32-bit CSDK application (aka Perl + DBI + DBD::Informix) to the 64-bit server. No harm done - but it wasn't actually necessary unless you've got a rule about 'only olipcshm connections' that you chose not to break. > So, sounds like 64 bit perl is a no-brainer and will link to DBD::Informix. Yes. I do it periodically. Last build was about 5.8.1. > What are the options to cause a 64 bit build of Perl, or is that too much to > expect off the top of your head? I tell it that my C compiler is 'gcc -m64' -- so my response to which is you C compiler is that, minus the quotes. The main reason I don't do it all the time in 64-bit is I haven't worked out how to get all the other libraries I use on occasion built and installed 64-bit. > I was worried about the suggestion that > going maximal 64 bit may cause compatibility problems with some modules. The problem arises if you plan to use a module Xyz::Pqr that was originally built for say Perl 5.8.2 with your new maximally 64-bit version of Perl. Actually, that maximally 64-bit stuff really applies to a 32-bit Perl -- not a 64-bit Perl. > If you are happy and have experience with 64 bit perl then I'll just > say YES to > all the questions next time I build? You have to know what's the correct way to address any non-ESQL/C 64-bit shared libraries. I always have to exclude /usr/local/* from my build since /usr/local is automounted (readonly, to boot) and contains gems such as Perl 5.004 and GCC 2.8. Yes; I've had no serious issues with 64-bit Perl. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/