| Issue 192: | installation errors as of 2.1.9 update | |
| 12 people starred this issue and may be notified of changes. | Back to list |
What steps will reproduce the problem? 1. Download .zip of either 2.1.9 or 2.1.8(maybe even others I only tried these two) 2. extract files 3. type python ./setup.py build install What is the expected output? What do you see instead? expected: successful installation received: running build running build_ext building 'pyodbcconf' extension gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DPYODBC_VERSION=2.1.9 -I/opt/python/2.5.6/include/python2.5 -c utils/pyodbcconf/pyodbcconf.cpp -o build/temp.linux-x86_64-2.5/utils/pyodbcconf/pyodbcconf.o -Wno-write-strings gcc: utils/pyodbcconf/pyodbcconf.cpp: No such file or directory gcc: no input files error: command 'gcc' failed with exit status 1 What version of the product are you using? On what operating system? Ubuntu 11.04 64bit I attempted this with newly downloaded 2.1.8 and 2.1.9 zips. Please provide any additional information below. The day before the 2.1.9 release I downloaded and installed 2.1.8 without any problems. I was on a new machine and had to setup the environment again, and when I attempted to install it using the same process as before I received the above error message. I RDP'd over to the initial machine and grabbed the 2.1.8 zip file I used there, thinking that maybe somehow the repository that the code was being retrieved from to create the zip file got corrupted. Using the 2.1.8 zip file I downloaded a day prior to the 2.1.9 update it installed immediately without any hiccups.
Jul 31, 2011
#1
victor.o...@gmail.com
Aug 1, 2011
I'm running into the same problem on ubuntu 10.04.3. I tried running "pip install pyodbc" and got the error above. Running "pip install https://github.com/mkleehammer/pyodbc/zipball/2.1.9" worked for me
Aug 26, 2011
Same problem on WinXP/Visual Studio. Same workaround as described by Collin on Aug 1st 2011.
Sep 13, 2011
Issue 209 has been merged into this issue.
Sep 13, 2011
Fixed in 2.1.11-beta01
Status:
Complete
|