Thanks, here are my two cents: Mini quick howto to connect to a sybase ASA/ASE: Get any 2.2 linux distro installed, except red hat 7 (compiler problems, it WILL fail). GET from Sybase the RPMs called sybase-common and sybase-openclient, the latest versions. Install them. do a link from /opt/sybase to /opt/sybase- {currentversion} which should exist now. make sure you have $SYBASE set in your profile, to /opt/sybase. Download zope-2.2.2.src.tgz untar as root, then chown -R root.root /path/to/Zopefolder make sure you have python and python-devel RPMs or DEBs. cd to zope folder run \\\'python w_pcgi.py\\\' run \\\'python zpasswd.py access\\\', enter username, password, CLEARTEXT encoding and no domain get ZSybaseDAv2 b2 and place the targz file into the zope folder do a \\\'tar zxvmf ZSybaseDAv2.tar.gz0 in the zope folder Once more do a chown -R root.root * cd into lib/python/Products/ZSybaseDAv2/src cp Setup.linux or Setup.solaris to Setup make -f Makefile.pre.in boot make cd to the parent folder (cd ..) cp src/sy_occ.so . enter python and try to do \\\'import sy_occ\\\' if it works and doesn\\\'t spit errors, you\\\'re set. exit python and go to the zope folder, then run ./start if zope starts, you\\\'re all set now there is an executable called /opt/sybase/bin/dsedit that you will have to use to create network transports. Fill in the appropriate data. Now for the problems. I managed to connect to an ASA 7.0 database, and retrieved successfully a select * from systable, but can\\\'t execute stored procedures, it spits some kind of another operation on progress error or unknown data type returned error. I assume ASA and dsclient are talking incompatible protocols here. Can someone help me? By the way, the data source created with dsedit for our ASE server works fine. Everything runs OK. Please reply and CC: me because I\\\'m kinda lagged behind with the mailing list and I need a reply soon. Thanks. I hope these instructions help people in connecting to Sybase, given the poor support they have in some countries (I\\\'m thinking mine). Manuel ---------------------------------------------------------- Universidad Federico Santa Maria - Campus Guayaquil Enviado por: www.usm.edu.ec
MANUEL JOSE AMADOR BRIZ wrote:
Thanks, here are my two cents:
Mini quick howto to connect to a sybase ASA/ASE:
Get any 2.2 linux distro installed, except red hat 7 (compiler problems, it WILL fail).
Only if you didn't read the RELEASE-NOTES. Use kgcc, it is the same compiler as RH 6.2 has. --- root@darwin in /root $ cat /etc/redhat-release Red Hat Linux release 6.2 (Zoot) root@darwin in /root $ gcc --version egcs-2.91.66 root@darwin in /root --- ucntcme@locutus in /home/ucntcme $ cat /etc/redhat-release Red Hat Linux release 7.0 (Guinness) ucntcme@locutus in /home/ucntcme $ kgcc --version egcs-2.91.66 --- ...
exit python and go to the zope folder, then run ./start
if zope starts, you\\\'re all set
not quite. You should stop zope, open a new terminal, and start zope from there. More often than not, you will need to set up the $SYBASE variables in the zope start up script. Running Zope in a 'clean' terminal will test the environment. -- E PLURIBUS LINUX
Which still sucks because most of the software will default to gcc, and compiled RPMs and binaries in other distributions fail sometimes too. but thanks for the tip. I tend to be something of a \"distracted professor\" (is that the way to put it?) sometimes. Quoting Bill Anderson <bill@noreboots.com>:
MANUEL JOSE AMADOR BRIZ wrote:
Thanks, here are my two cents:
Mini quick howto to connect to a sybase ASA/ASE:
Get any 2.2 linux distro installed, except red hat 7 (compiler
problems, it
WILL fail).
Only if you didn\'t read the RELEASE-NOTES. Use kgcc, it is the same compiler as RH 6.2 has.
--- root@darwin in /root $ cat /etc/redhat-release Red Hat Linux release 6.2 (Zoot) root@darwin in /root $ gcc --version egcs-2.91.66 root@darwin in /root --- ucntcme@locutus in /home/ucntcme $ cat /etc/redhat-release Red Hat Linux release 7.0 (Guinness) ucntcme@locutus in /home/ucntcme $ kgcc --version egcs-2.91.66 ---
...
exit python and go to the zope folder, then run ./start
if zope starts, you\\\\\\\'re all set
not quite. You should stop zope, open a new terminal, and start zope from there. More often than not, you will need to set up the $SYBASE variables in the zope start up script. Running Zope in a \'clean\' terminal will test the environment.
-- E PLURIBUS LINUX
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
---------------------------------------------------------- Universidad Federico Santa Maria - Campus Guayaquil Enviado por: www.usm.edu.ec
MANUEL JOSE AMADOR BRIZ wrote:
Which still sucks because most of the software will default to gcc, and compiled RPMs and binaries in other distributions fail sometimes too.
In your Profile (bash example): $export CC=kgcc and Bob's yer uncle. :) ( doing this, any ./configure you run will pick up kgcc instead of gcc ) If a binary was compiled on a seperate system/distribution, and fails on yours, you can't blame _your_ compiler, 'cuz it didn't do it. :) -- E PLURIBUS LINUX
participants (3)
-
Bill Anderson -
Bill Anderson -
MANUEL JOSE AMADOR BRIZ