google-code-export / pymssql

Automatically exported from code.google.com/p/pymssql
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Build still fails for 64-bit CentOS #76

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
In tarball pymssql-2.0.0b1-dev-20111019.tar.gz, 64-bit build still has problem 
described in #72. Possibly files in freetds/nix_64/* were not updated:

nix_32/lib:
-rw-r--r-- 1 1000 1000 1528394 Oct 18 06:21 libsybdb.a

nix_64/lib:
-rw-r--r-- 1 1000 1000 2169356 Oct 17 06:49 libsybdb.a

What worked for me (I have freetds 0.91-1.el5 installed):
1. rm freetds/nix_64/lib/libsybdb.a
2. ln -s /usr/lib64/libsybdb.so.5.0.0 /usr/lib64/libsybdb.so
3. python26 setup.py clean
4. python26 setup.py build
5. python26 setup.py install

I've added this comment to #72, but it didn't reopen the issue - opening new 
one.

Original issue reported on code.google.com by m.maly...@gmail.com on 6 Dec 2011 at 12:28

GoogleCodeExporter commented 9 years ago
Where is /usr/lib64/libsybdb.so.5.0.0 coming from?  Is that a FreeTDS you have 
built yourself?

Original comment by rsyr...@gmail.com on 8 Mar 2012 at 2:41

GoogleCodeExporter commented 9 years ago
Issue 82 has been merged into this issue.

Original comment by rsyr...@gmail.com on 8 Mar 2012 at 2:43

GoogleCodeExporter commented 9 years ago

Original comment by rsyr...@gmail.com on 8 Mar 2012 at 2:48

GoogleCodeExporter commented 9 years ago
No, it is from Fedora Project rpm (freetds-0.91-1.el5.x86_64.rpm) downloaded 
with yum. It should be in epel repository.

Original comment by m.maly...@gmail.com on 8 Mar 2012 at 2:50

GoogleCodeExporter commented 9 years ago
Is this still happening now, as there have been a number of changes lately...?

I was just able to install pymssql on a CentOS 6.3 system. What version of 
CentOS do you have?

Original comment by msabr...@gmail.com on 14 Jan 2013 at 6:15

GoogleCodeExporter commented 9 years ago
fails on 6.4 
2.6.32-358.2.1.el6.x86_64

distutils.errors.DistutilsError: Setup script exited with error: command 'gcc' 
failed with exit status 1

----------------------------------------
Command python setup.py egg_info failed with error code 1 in 
/tmp/pip-build-root/pymssql
Storing complete log in /root/.pip/pip.log

Original comment by Santek...@gmail.com on 4 Apr 2013 at 3:30

GoogleCodeExporter commented 9 years ago
Is this still happening?

Original comment by msabr...@gmail.com on 7 Aug 2013 at 3:06

GoogleCodeExporter commented 9 years ago

Original comment by msabr...@gmail.com on 7 Aug 2013 at 3:16

GoogleCodeExporter commented 9 years ago
This is still failing.  

mssqldbmodule.c:88: error: redefinition of typedef ‘LPBYTE’

/usr/include/freetds/sqlfront.h:35: note: previous declaration of ‘LPBYTE’ 
was here

error: command 'gcc' failed with exit status 1

Prior to this I install freetds-devel with yum and also added the include path 
to /etc/ld.so.conf.d/freetds-x84_64.conf.  The include path is 
/usr/include/freetds.

Original comment by bravofox...@gmail.com on 9 Aug 2013 at 3:22

GoogleCodeExporter commented 9 years ago
@bravofoxtrot35,

"mssqldbmodule.c" - if I'm not mistaken, that sounds like an error message from 
an old 1.x pre-Cython version of pymssql (which I don't want to support). What 
steps did you take to reach this error?

Original comment by msabr...@gmail.com on 11 Aug 2013 at 1:20

GoogleCodeExporter commented 9 years ago
Sorry this was my mistake.  I didn't have Cython properly installed into the 
virtualenv.

Original comment by bravofox...@gmail.com on 14 Aug 2013 at 5:06

GoogleCodeExporter commented 9 years ago
Going to mark this as fixed since m.malycha cannot reproduce anymore nor can 
bravofoxtrot35

From: Maciej Malycha <m.malycha...>
Date: August 14, 2013, 10:37:53 AM PDT
To: Marc Abramowitz <msabramo...>
Subject: Re: Pymssql

I have tested both pymssql-2.0.0b1-dev-20111019.tar.gz where the issue was 
found and newest pymssql-2.0.0b1-dev-20130403.tar.gz on the 64-bit CentOS 6.4, 
but I was unable to reproduce the problem. Previously I was using CentOS 5.6, 
so probably it was CentOS/environment problem, not the pymssql.

Original comment by msabr...@gmail.com on 14 Aug 2013 at 8:26