Published by nick on 26 Oct 2007 at 12:36 am
Installing Trac with subversion on Cent OS 5
Trac is decent bug tracking software that is getting a lot of attention these days. It’s very simple to use, which I like. It includes subversion integration so that you can walk through your source code tree and view diffs from one version to another. Handy.
However, Trac’s installation process has a lot of room for improvement in the simplicity department. Here are the steps I went through to install trac on Cent OS 5. I captured them so that others may find it easier to get Trac up and running. Enjoy.
If these instructions work for you, please leave a comment! If they don’t, please leave a comment!
- Install python and its goodies.
- Use yum to install the base package:
yum install python - Install mod_python. This is so Apache can run the python scripts as a module:
yum install mod_python - Install MySQL-python so that python can interact with mysql
- Download and untar MySQL-python from http://sourceforge.net/projects/mysql-python
cd $mysqlpythonsourcedirpython setup.py build && python setup.py install
- Use yum to install the base package:
- Install some devel packages that are needed for compiling trac and svn integration:
yum install neon neon-devel python-devel swig - Install Clearsilver, a templating package that trac depends on.
- Download and untar clearsilver from http://www.clearsilver.net/downloads/
- Compile
cd $clearsilversourcedir; ./configure && make && make install
- Install trac!
- Download and untar trac from http://trac.edgewall.org/wiki/TracDownload
cd $tracsourcedir; python ./setup.py install- Initialize your first trac project:
trac-admin $pathtoyourtracproject initenv - Tell Apache about trac.. Add the following lines to your Apache configuration file:
<Location /> SetHandler mod_python PythonHandler trac.web.mod python_frontend PythonOption TracEnv $pathtoyourtracproject PythonOption TracUriRoot /trac/ </Location>
Finally, restart httpd and try it out by going to:
http://$yourhost/trac/
If it doesn’t work, check your webserver error log for errors: tail -f /var/log/httpd/error_log
Again, please leave a comment so that you may help others with the same problems you have.
Daniel Skinner on 14 Dec 2007 at 12:38 pm #
The guide is working well for me so far. I have a problem with trac-admin however.
When running initenv it asks for the ‘Templates directory’. The default value is a windows path and I have no idea what it should be for CentOS. Any ideas?
nick on 14 Dec 2007 at 1:45 pm #
Daniel,
Happy to help.
You are running this line:
trac-admin $pathtoyourtracproject initenv
Are you running it literally? You are supposed to replace $pathtoyourproject with an empty directory that you create for where want to store your trac data.
I didn’t make that clear in the docs, I’ll update.
Daniel Skinner on 14 Dec 2007 at 4:35 pm #
It was clear enough to me, I did it right. It seemed like all the environment variables were Windows-like.
I think this is because I tried Trac’s easy_install method first and it messed it up.
I have started from a fresh CentOS install and am about to install svn/trac using your guide. I will keep you updated.
Daniel Skinner on 14 Dec 2007 at 4:52 pm #
Nick,
I got it working. Thanks for the help and the awesome guide, it was exactly what I was looking for.
Here is what I did (for anyone else):
- Fresh install of CentOS 5 (running as a virtual machine).
- Followed the CentOS 5 Perfect Setup Guide.
-
yum install subversion- Created a subversion repository with
svnadmin create- Followed this guide word for word (except for the Apache configuration, I needed a different solution).
- I also used parts of CentOS, Subversion How-To (setting up Apache and SVN) and Trac on Fedora Guide (setting up Apache and Trac).
I don’t think following the ‘Perfect Setup Guide’ is required at all - it’s just what I did.
Thanks
Daniel Skinner on 14 Dec 2007 at 5:53 pm #
I spoke to soon. This might be outside the focus of your guide but I’m stuck at the moment. I have set up Trac with apache and when I try to view Trac in a web browser I get the following:
Traceback (most recent call last):File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
dispatcher.dispatch(req)
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 206, in dispatch
req.hdf = HDFWrapper(loadpaths=chrome.get_all_templates_dirs())
File "/usr/lib/python2.4/site-packages/trac/web/clearsilver.py", line 135, in __init__
raise TracError, "ClearSilver not installed (%s)" % e
TracError: ClearSilver not installed (No module named neo_cgi)
Any ideas?
Daniel Skinner on 14 Dec 2007 at 5:58 pm #
Ok, again I was too hasty with the comment button!
Here is what I did to fix it:
wget http://dag.wieers.com/rpm/packages/clearsilver/clearsilver-0.10.4-1.el5.rf.i386.rpm
rpm -i clearsilver-0.10.4-1.el5.rf.i386.rpm
wget http://dag.wieers.com/rpm/packages/clearsilver/python-clearsilver-0.10.4-1.el5.rf.i386.rpm
rpm -i clearsilver-0.10.4-1.el5.rf.i386.rpm
Setup Subversion and Trac on CentOS 5 | Daniel Skinner: News and Articles on Web Development on 06 Jan 2008 at 10:19 am #
[…] Install Trac: Follow Nick’s guide with the alternative Clearsilver installation below. Skip the Apache Configuration […]
sushmi on 18 Jan 2008 at 4:31 am #
I installed trac with subversion+apache. During the execution of "trac-admin" for database string i gave "mysql://root:a@localhost:3306/trac"
since i used mysql database but during environment creation the following error occured.
Please enter location of Trac page templates.
Default is the location of the site-wide templates installed with Trac.
Templates directory [/usr/local/share/trac/templates]>
Creating and Initializing Project
Failed to create environment. No module named MySQLdb
Traceback (most recent call last):
File "/usr/local/lib/python2.4/site-packages/trac/scripts/admin.py", line 613, in do_initenv
options=options)
File "/usr/local/lib/python2.4/site-packages/trac/env.py", line 145, in __init__
self.create(options)
File "/usr/local/lib/python2.4/site-packages/trac/env.py", line 250, in create
DatabaseManager(self).init_db()
File "/usr/local/lib/python2.4/site-packages/trac/db/api.py", line 70, in init_db
connector.init_db(**args)
File "/usr/local/lib/python2.4/site-packages/trac/db/mysql_backend.py", line 44, in init_db
cnx = self.get_connection(path, user, password, host, port, params)
File "/usr/local/lib/python2.4/site-packages/trac/db/mysql_backend.py", line 40, in get_connection
return MySQLConnection(path, user, password, host, port, params)
File "/usr/local/lib/python2.4/site-packages/trac/db/mysql_backend.py", line 132, in __init__
import MySQLdb
ImportError: No module named MySQLdb
Failed to initialize environment. 1
Traceback (most recent call last):
File "/usr/local/lib/python2.4/site-packages/trac/scripts/admin.py", line 617, in do_initenv
sys.exit(1)
SystemExit: 1
=================
Any idea, please help me out!
Sushmi
nick on 18 Jan 2008 at 11:30 am #
Based on the error message, it looks like you may have skipped this step:
3. Install MySQL-python so that python can interact with mysql.
Download and untar MySQL-python from http://sourceforge.net/projects/mysql-python
cd $mysqlpythonsourcedir
python setup.py build && python setup.py install
Daniel Schiavone on 21 Jan 2008 at 2:28 pm #
After installation I’m getting the following errors…
[Mon Jan 21 16:18:08 2008] [error] [client 66.93.119.89] PythonHandler trac.web.mod: Traceback (most recent call last):
[Mon Jan 21 16:18:08 2008] [error] [client 66.93.119.89] PythonHandler trac.web.mod: File "/usr/lib64/python2.4/site-packages/mod_python/apache.py", line 287, in HandlerDispatch\n log=debug)
[Mon Jan 21 16:18:08 2008] [error] [client 66.93.119.89] PythonHandler trac.web.mod: File "/usr/lib64/python2.4/site-packages/mod_python/apache.py", line 461, in import_module\n f, p, d = imp.find_module(parts[i], path)
[Mon Jan 21 16:18:08 2008] [error] [client 66.93.119.89] PythonHandler trac.web.mod: ImportError: No module named mod
My httpd.conf reads…
SetHandler mod_python
# added the following line
PythonInterpreter main_interpreter
PythonHandler trac.web.mod python_frontend
PythonOption TracEnv /var/www/trac/project1
PythonOption TracUriRoot /trac/
Daniel Schiavone on 21 Jan 2008 at 2:31 pm #
Looks like the space in PythonHandler trac.web.mod python_frontend was screwing it up. I removed it and now getting…
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
dispatcher.dispatch(req)
File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 206, in dispatch
req.hdf = HDFWrapper(loadpaths=chrome.get_all_templates_dirs())
File "/usr/lib/python2.4/site-packages/trac/web/clearsilver.py", line 135, in __init__
raise TracError, "ClearSilver not installed (%s)" % e
TracError: ClearSilver not installed (No module named neo_cgi)
Which someone solved above I believe.
nick on 21 Jan 2008 at 3:12 pm #
Daniel Schiavone: Based on the error message, it looks like Clearsilver is not installed. You may have skipped this step:
3. Install Clearsilver, a templating package that trac depends on.
1. Download and untar clearsilver from http://www.clearsilver.net/downloads/
2. Compile
cd $clearsilversourcedir; ./configure && make && make install
-Nick
gabe on 24 Jan 2008 at 1:26 pm #
Thanks for the guide… 2 small issues I ran into, I needed to install python-devel before installing MySQL-python, and I needed to recompile my MySQL installation with the option: –enable-thread-safe-client Below are the errors I got:
Error:
In file included from _mysql.c:29:pymemcompat.h:10:20: error: Python.h: No such file or directory
Fix: install the python-devel package before setup/install of MySQL-python
Error: /usr/bin/ld: cannot find -lmysqlclient_r
Fix: recompile mysql with –enable-thread-safe-client
Otherwise, it went smoothly. Piece of cake.
Shack Dougall on 08 Feb 2008 at 10:29 pm #
Great instructions! Thanks!
I couldn’t get mod_python to work with Trac. It never gave me an error message, but just silently failed. Possibly, it was related to the fact that I have a WordPress blog at the root of my website which does a lot of url rewriting.
Anyway, mod_wsgi is also simple to setup and worked immediately for me.
joel on 25 Feb 2008 at 8:31 pm #
This is what I used.
SetHandler mod_python
PythonHandler trac.web.modpython_frontend
PythonOption TracEnv /srv/trac
PythonOption TracUriRoot /trac
SetEnv PYTHON_EGG_CACHE /srv/trac/cache
PythonDebug On
The space in the PythonHandler line was causing me problems. I also needed to add the PYTHON_EGG_CACHE line.
Badoviatgat on 24 Mar 2008 at 4:11 am #
I’d prefer reading in my native language, because my knowledge of your languange is no so well.
Richard on 29 Mar 2008 at 2:27 pm #
I only got as far as "python setup.py build && python setup.py install"
and got a shed load of errors, such as:
_mysql.c:545: warning: statement with no effect
_mysql.c:546: warning: implicit declaration of function ‘mysql_init’
_mysql.c:546: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:546: warning: statement with no effect
_mysql.c:549: warning: implicit declaration of function ‘mysql_options’
_mysql.c:549: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:549: error: ‘MYSQL_OPT_CONNECT_TIMEOUT’ undeclared (first use in this function)
_mysql.c:553: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:553: error: ‘MYSQL_OPT_COMPRESS’ undeclared (first use in this function)
_mysql.c:554: error: ‘CLIENT_COMPRESS’ undeclared (first use in this function)
_mysql.c:554: error: invalid operands to binary |
_mysql.c:554: error: incompatible types in assignment
_mysql.c:554: warning: statement with no effect
_mysql.c:557: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:557: error: ‘MYSQL_OPT_NAMED_PIPE’ undeclared (first use in this function)
_mysql.c:558: warning: comparison of distinct pointer types lacks a cast
_mysql.c:559: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:559: error: ‘MYSQL_INIT_COMMAND’ undeclared (first use in this function)
_mysql.c:560: warning: comparison of distinct pointer types lacks a cast
_mysql.c:561: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:561: error: ‘MYSQL_READ_DEFAULT_FILE’ undeclared (first use in this function)
etc. etc.
any ideas or help would be much appreciated
Vu Huy Phuong on 03 Apr 2008 at 2:15 am #
to Richard:
I have had the same errors with you, I read the README file and found that I should install mysql-devel (and python-devel if neccesary) package before, then I tried and it’s solved. Try it yourself and let me know!
John on 15 Apr 2008 at 7:03 pm #
for some reason even after I installed mod_python I get
Invalid command ‘PythonHandler’, perhaps misspelled or defined by a module not included in the server configuration
I checked in my /usr/local/apache/modules and mod_python.so isn’t there… so whether I do a yum install or manually compile mod_python it never gets installed in the modules directory…
any suggestions??
John on 15 Apr 2008 at 7:25 pm #
nevermind, for some reason ./configure –with-apxs=/usr/local/apache/bin/apxs before compiling made it work…
John on 15 Apr 2008 at 7:49 pm #
well now I get another problem…
using
SetHandler mod_python
PythonHandler trac.web.modpython_frontend
PythonOption TracEnv $pathtoyourtracproject
PythonOption TracUriRoot /trac/
where $pathtoyourtracproject is replaced by my path, I get an 500 internal error on my server… any clue why?
Pieter on 16 May 2008 at 6:39 am #
I’m having the same problem as John. I get a 500 internal error.
The output of /var/log/httpd/error_log
[Fri May 16 15:49:00 2008] [error] [client 10.10.3.18] PythonHandler trac.web.mod: ImportError: No module named mod
[Fri May 16 15:49:04 2008] [error] [client 10.10.3.18] PythonHandler trac.web.mod: Traceback (most recent call last):
[Fri May 16 15:49:04 2008] [error] [client 10.10.3.18] PythonHandler trac.web.mod: File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 287, in HandlerDispatch\n log=debug)
[Fri May 16 15:49:04 2008] [error] [client 10.10.3.18] PythonHandler trac.web.mod: File "/usr/lib/python2.4/site-packages/mod_python/apache.py", line 461, in import_module\n f, p, d = imp.find_
module(parts[i], path)
[Fri May 16 15:49:04 2008] [error] [client 10.10.3.18] PythonHandler trac.web.mod: ImportError: No module named mod
Pieter on 16 May 2008 at 7:49 am #
The problem I was having was the following:
The Python egg cache directory is currently set to: /root/.python-eggs
Perhaps your account does not have write access to this directory? You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory.
So I made a directory under /usr/lib/trac/plugins-cache with the right permissions (777) so that the Apache user can write into it.
I’ve added in my httpd.conf:
SetEnv PYTHON_EGG_CACHE /usr/lib/trac/plugin-cache
Restarted Apache and tadaaaa, it works!
More info about Trac Plugins/Problems here: http://trac.edgewall.org/wiki/TracPlugins
Installing Trac on CentOS 5 « Compulsivo, Inc. on 16 May 2008 at 4:41 pm #
[…] (because it sucks and has been slain by Git). If you need SVN support, check out the posts by Nick or Daniel […]
Wei-Yin Chen on 18 May 2008 at 3:10 pm #
If you have Dag repository set up, you may just do "yum install trac" and most of the tedious steps can be skipped.
Frank Helsley on 27 Jun 2008 at 3:16 pm #
Do you want to do some consulting work with a trac & svn migration to new hardware? I am an owner of an IT support firm in Austin, TX area and might need someone with more trav/svn expertise than I. I can probably figure it all out, but it might take longer, and I could probably learn some things by getting someone else involved…
wil on 28 Jul 2008 at 4:29 pm #
I am new to linux and have a few questions in setting up TRAC on a Linux server.
when you say: "cd $mysqlpythonsourcedir "
where do you suggest we install/unzip the tar packages? (this is for mysqlpython, clearsilver and trac?
(also, how do we unzip the tar package? do we paste it in through the ftp first, before going through terminal?)
nick on 28 Jul 2008 at 10:23 pm #
$mypythonsourcedir is /usr/local/src/$pythonversion for me.
To untar on unix command line, use "tar -xzvf $tarfile"
wil on 29 Jul 2008 at 9:56 pm #
When creating your TRAC and SVN projects ("trac-admin $pathtoyourtracproject initenv"), should you be doing it in your public folder? (ie. /home/domain/public_html/trac/)
once i’ve done this I should be able access trac through http://domain/trac/ corrrect? When I try to access, i simply see a listing of folders and files in the directoy and no html.
…also is there a way i can clean out and revert back to the original config files as I am not sure if the changes I made were correct.
thanks for the help.
AlexM on 17 Aug 2008 at 8:16 am #
Your blog is interesting!
Keep up the good work!
Installing Trac on CentOS 5 | Compulsivo on 25 Sep 2008 at 1:22 pm #
[…] (because it sucks and has been slain by Git). If you need SVN support, check out the posts by Nick or Daniel […]
Michelangelo on 29 Oct 2008 at 4:53 pm #
Hi Nick, there is a mistake at the line: PythonHandler trac.web.mod python_frontend
You have to write: PythonHandler trac.web.modpython_frontend
and if u want to protect the Trac page use:
SetHandler mod_python
PythonHandler trac.web.modpython_frontend
PythonOption TracEnv /home/trac/
PythonOption TracUriRoot /
AuthType Basic
AuthName "TRAC Dashboard"
AuthUserFile /etc/subversion/passwd
Require valid-user
chrisw on 03 Dec 2008 at 11:50 pm #
Need to install mysql-devel so that you can install MySQL-python-1.2.2
Personal Tracker » Blog Archive » Panduan Subversion dan Trac di Centos 5.2 on 11 Dec 2008 at 9:07 pm #
[…] http://www.techyouruniverse.com/software/installing-trac-with-subversion-on-cent-os-5-with-neon-and-… […]
Rubén Ortiz » Instalar TRAC en CentOS 5 on 20 Jan 2009 at 5:06 am #
[…] http://www.techyouruniverse.com/ […]
Rubén Ortiz on 20 Jan 2009 at 9:25 am #
Hi
I linked your post to my blog, I have wroted a guide to spanish users. Let me ask you (and your readers) one question. To login to TRAC, you need to add a user through httpasswd -m /path/to/proyect username and combinating Apache setup, you can … ask for a password with directive AuthUserFile /srv/trac/project.htpasswd.
But Trac have a DB users on SQLite, so the users of Apache(when you login to trac) and users of DB SQLite are not the same, aren’t they?
I think is a confusing topic. Because to add a normal user to Trac, first you need to add user and password through htpasswd and later create the same user in Trac(the user is created then on DB with permissions).
Thanks by your post
Was very helpful
Instalar TRAC en CentOS 5 | Blog of SysAdmins on 20 Jan 2009 at 11:32 am #
[…] http://www.techyouruniverse.com/ […]
Kwasi on 05 Feb 2009 at 2:15 am #
I get the following when trying to install mod_python on Apache 2.2.11
–> Running transaction check
—> Package mod_python.i386 0:3.2.8-3.1 set to be updated
–> Processing Dependency: httpd >= 2.0.40 for package: mod_python
–> Processing Dependency: httpd-mmn = 20051115 for package: mod_python
–> Finished Dependency Resolution
Error: Missing Dependency: httpd >= 2.0.40 is needed by package mod_python
Error: Missing Dependency: httpd-mmn = 20051115 is needed by package mod_python
walter on 01 Apr 2009 at 7:43 am #
Instead step 3.1 , 3.2 and 4.1 I did this http://madboa.com/geek/trac-centos/#system-packages
then:
yum –enablerepo=dag –enablerepo=kbs-CentOS-Extras install trac
Mathieu on 12 May 2009 at 6:07 am #
Just a quick reminder that you have to install gcc, and maybe run a "yum install mysql*" to be able to build mysql-python.
Ian Masters on 10 Jun 2009 at 11:38 pm #
It now seems possible (at least on CentOS 5.2) to do all the installing via yum, e.g.:
yum install python mod_python
yum install MySQL-python
yum install neon neon-devel python-devel swig
yum install clearsilver
yum install trac
Dawson on 14 Jun 2009 at 2:31 am #
I have mysql-devel installed, but I get the following when running, any ideas?
python setup.py build && python setup.py install
running build
running build_py
copying MySQLdb/release.py -> build/lib.linux-x86_64-2.4/MySQLdb
running build_ext
building ‘_mysql’ extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector –param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fPIC -Dversion_info=(1,2,2,’final’,0) -D__version__=1.2.2 -I/usr/include/mysql -I/usr/include/python2.4 -c _mysql.c -o build/temp.linux-x86_64-2.4/_mysql.o -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector –param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -fno-strict-aliasing -fwrapv
In file included from _mysql.c:29:
pymemcompat.h:10:20: error: Python.h: No such file or directory
_mysql.c:30:26: error: structmember.h: No such file or directory
In file included from /usr/include/mysql/mysql.h:43,
from _mysql.c:40:
/usr/include/sys/types.h:153: error: duplicate ‘unsigned’
/usr/include/sys/types.h:153: error: two or more data types in declaration specifiers
_mysql.c:64: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:65: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:66: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:67: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:68: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:69: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:70: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:71: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:72: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:73: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:74: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:77: error: expected specifier-qualifier-list before ‘PyObject_HEAD’
_mysql.c:87: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ConnectionObject_Type’
_mysql.c:90: error: expected specifier-qualifier-list before ‘PyObject_HEAD’
_mysql.c:98: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ResultObject_Type’
_mysql.c:107: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:229: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:320: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:338: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:361: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c:362: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c: In function ‘_mysql_ResultObject_Initialize’:
_mysql.c:364: error: ‘NULL’ undeclared (first use in this function)
_mysql.c:364: error: (Each undeclared identifier is reported only once
_mysql.c:364: error: for each function it appears in.)
_mysql.c:366: warning: initialization from incompatible pointer type
_mysql.c:368: error: ‘PyObject’ undeclared (first use in this function)
_mysql.c:368: error: ‘conv’ undeclared (first use in this function)
_mysql.c:368: error: invalid operands to binary *
_mysql.c:368: warning: statement with no effect
_mysql.c:372: warning: implicit declaration of function ‘PyArg_ParseTupleAndKeywords’
_mysql.c:372: error: ‘args’ undeclared (first use in this function)
_mysql.c:372: error: ‘kwargs’ undeclared (first use in this function)
_mysql.c:375: warning: implicit declaration of function ‘PyDict_New’
_mysql.c:375: warning: statement with no effect
_mysql.c:377: error: ‘_mysql_ResultObject’ has no member named ‘conn’
_mysql.c:377: error: expected expression before ‘)’ token
_mysql.c:377: error: invalid operands to binary *
_mysql.c:377: warning: statement with no effect
_mysql.c:378: warning: implicit declaration of function ‘Py_INCREF’
_mysql.c:379: error: ‘_mysql_ResultObject’ has no member named ‘use’
_mysql.c:379: warning: statement with no effect
_mysql.c:380: error: ‘Py_BEGIN_ALLOW_THREADS’ undeclared (first use in this function)
_mysql.c:380: warning: statement with no effect
_mysql.c:382: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:382: warning: passing argument 1 of ‘mysql_use_result’ from incompatible pointer type
_mysql.c:384: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:384: warning: passing argument 1 of ‘mysql_store_result’ from incompatible pointer type
_mysql.c:385: error: ‘_mysql_ResultObject’ has no member named ‘result’
_mysql.c:385: warning: statement with no effect
_mysql.c:386: error: ‘Py_END_ALLOW_THREADS’ undeclared (first use in this function)
_mysql.c:386: warning: statement with no effect
_mysql.c:388: error: ‘_mysql_ResultObject’ has no member named ‘converter’
_mysql.c:388: warning: implicit declaration of function ‘PyTuple_New’
_mysql.c:388: warning: statement with no effect
_mysql.c:392: error: ‘_mysql_ResultObject’ has no member named ‘nfields’
_mysql.c:392: warning: statement with no effect
_mysql.c:393: error: ‘_mysql_ResultObject’ has no member named ‘converter’
_mysql.c:396: error: ‘tmp’ undeclared (first use in this function)
_mysql.c:396: error: invalid operands to binary *
_mysql.c:396: error: ‘fun’ undeclared (first use in this function)
_mysql.c:396: warning: left-hand operand of comma expression has no effect
_mysql.c:396: warning: statement with no effect
_mysql.c:397: warning: implicit declaration of function ‘PyInt_FromLong’
_mysql.c:397: warning: statement with no effect
_mysql.c:399: warning: implicit declaration of function ‘PyObject_GetItem’
_mysql.c:399: warning: statement with no effect
_mysql.c:400: warning: implicit declaration of function ‘Py_DECREF’
_mysql.c:402: warning: implicit declaration of function ‘PyErr_Clear’
_mysql.c:403: error: ‘Py_None’ undeclared (first use in this function)
_mysql.c:403: warning: statement with no effect
_mysql.c:406: warning: implicit declaration of function ‘PySequence_Check’
_mysql.c:407: warning: implicit declaration of function ‘PySequence_Size’
_mysql.c:408: error: ‘fun2’ undeclared (first use in this function)
_mysql.c:408: error: invalid operands to binary *
_mysql.c:408: warning: statement with no effect
_mysql.c:410: error: ‘t’ undeclared (first use in this function)
_mysql.c:410: error: invalid operands to binary *
_mysql.c:410: warning: implicit declaration of function ‘PySequence_GetItem’
_mysql.c:410: warning: statement with no effect
_mysql.c:412: warning: implicit declaration of function ‘PyTuple_Check’
_mysql.c:413: warning: implicit declaration of function ‘PyTuple_GET_SIZE’
_mysql.c:415: error: ‘pmask’ undeclared (first use in this function)
_mysql.c:415: error: invalid operands to binary *
_mysql.c:415: warning: statement with no effect
_mysql.c:416: warning: implicit declaration of function ‘PyTuple_GET_ITEM’
_mysql.c:416: warning: statement with no effect
_mysql.c:417: warning: statement with no effect
_mysql.c:418: warning: implicit declaration of function ‘PyInt_Check’
_mysql.c:419: warning: implicit declaration of function ‘PyInt_AS_LONG’
_mysql.c:433: warning: statement with no effect
_mysql.c:436: warning: statement with no effect
_mysql.c:438: warning: implicit declaration of function ‘PyTuple_SET_ITEM’
_mysql.c:438: error: ‘_mysql_ResultObject’ has no member named ‘converter’
_mysql.c: In function ‘_mysql_ResultObject_clear’:
_mysql.c:462: warning: implicit declaration of function ‘Py_XDECREF’
_mysql.c:462: error: ‘_mysql_ResultObject’ has no member named ‘converter’
_mysql.c:463: error: ‘_mysql_ResultObject’ has no member named ‘converter’
_mysql.c:463: error: ‘NULL’ undeclared (first use in this function)
_mysql.c:463: warning: statement with no effect
_mysql.c:464: error: ‘_mysql_ResultObject’ has no member named ‘conn’
_mysql.c:465: error: ‘_mysql_ResultObject’ has no member named ‘conn’
_mysql.c:465: warning: statement with no effect
_mysql.c: At top level:
_mysql.c:472: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c:473: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c: In function ‘_mysql_ConnectionObject_Initialize’:
_mysql.c:475: error: ‘NULL’ undeclared (first use in this function)
_mysql.c:475: warning: initialization from incompatible pointer type
_mysql.c:476: error: ‘PyObject’ undeclared (first use in this function)
_mysql.c:476: error: ‘conv’ undeclared (first use in this function)
_mysql.c:476: error: invalid operands to binary *
_mysql.c:476: warning: statement with no effect
_mysql.c:477: error: ‘ssl’ undeclared (first use in this function)
_mysql.c:477: error: invalid operands to binary *
_mysql.c:477: warning: statement with no effect
_mysql.c:479: warning: initialization from incompatible pointer type
_mysql.c:479: warning: initialization from incompatible pointer type
_mysql.c:479: warning: initialization from incompatible pointer type
_mysql.c:480: warning: initialization from incompatible pointer type
_mysql.c:480: warning: initialization from incompatible pointer type
_mysql.c:482: warning: initialization from incompatible pointer type
_mysql.c:482: warning: initialization from incompatible pointer type
_mysql.c:482: warning: initialization from incompatible pointer type
_mysql.c:483: warning: initialization from incompatible pointer type
_mysql.c:483: warning: initialization from incompatible pointer type
_mysql.c:493: error: initializer element is not constant
_mysql.c:493: error: (near initialization for ‘kwlist[16]’)
_mysql.c:496: warning: initialization from incompatible pointer type
_mysql.c:497: warning: initialization from incompatible pointer type
_mysql.c:498: warning: initialization from incompatible pointer type
_mysql.c:500: error: ‘_mysql_ConnectionObject’ has no member named ‘converter’
_mysql.c:500: warning: statement with no effect
_mysql.c:501: error: ‘_mysql_ConnectionObject’ has no member named ‘open’
_mysql.c:501: warning: statement with no effect
_mysql.c:502: warning: implicit declaration of function ‘_mysql_Exception’
_mysql.c:503: error: ‘args’ undeclared (first use in this function)
_mysql.c:503: error: ‘kwargs’ undeclared (first use in this function)
_mysql.c:517: warning: statement with no effect
_mysql.c:524: error: ‘_mysql_ConnectionObject’ has no member named ‘converter’
_mysql.c:524: warning: statement with no effect
_mysql.c:532: error: ‘value’ undeclared (first use in this function)
_mysql.c:532: error: invalid operands to binary *
_mysql.c:532: warning: statement with no effect
_mysql.c:533: warning: implicit declaration of function ‘PyMapping_GetItemString’
_mysql.c:533: warning: statement with no effect
_mysql.c:533: warning: implicit declaration of function ‘PyString_AsString’
_mysql.c:533: warning: assignment makes pointer from integer without a cast
_mysql.c:534: warning: statement with no effect
_mysql.c:534: warning: assignment makes pointer from integer without a cast
_mysql.c:535: warning: statement with no effect
_mysql.c:535: warning: assignment makes pointer from integer without a cast
_mysql.c:536: warning: statement with no effect
_mysql.c:536: warning: assignment makes pointer from integer without a cast
_mysql.c:537: warning: statement with no effect
_mysql.c:537: warning: assignment makes pointer from integer without a cast
_mysql.c:545: error: ‘Py_BEGIN_ALLOW_THREADS’ undeclared (first use in this function)
_mysql.c:545: warning: statement with no effect
_mysql.c:546: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:546: warning: passing argument 1 of ‘mysql_init’ from incompatible pointer type
_mysql.c:549: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:550: warning: passing argument 1 of ‘mysql_options’ from incompatible pointer type
_mysql.c:553: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:553: warning: passing argument 1 of ‘mysql_options’ from incompatible pointer type
_mysql.c:557: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:557: warning: passing argument 1 of ‘mysql_options’ from incompatible pointer type
_mysql.c:558: warning: comparison of distinct pointer types lacks a cast
_mysql.c:559: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:559: warning: passing argument 1 of ‘mysql_options’ from incompatible pointer type
_mysql.c:560: warning: comparison of distinct pointer types lacks a cast
_mysql.c:561: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:561: warning: passing argument 1 of ‘mysql_options’ from incompatible pointer type
_mysql.c:562: warning: comparison of distinct pointer types lacks a cast
_mysql.c:563: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:563: warning: passing argument 1 of ‘mysql_options’ from incompatible pointer type
_mysql.c:566: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:566: warning: passing argument 1 of ‘mysql_options’ from incompatible pointer type
_mysql.c:570: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:571: warning: passing argument 1 of ‘mysql_ssl_set’ from incompatible pointer type
_mysql.c:574: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:575: warning: passing argument 1 of ‘mysql_real_connect’ from incompatible pointer type
_mysql.c:577: error: ‘Py_END_ALLOW_THREADS’ undeclared (first use in this function)
_mysql.c:577: warning: statement with no effect
_mysql.c:589: error: ‘_mysql_ConnectionObject’ has no member named ‘open’
_mysql.c:589: warning: statement with no effect
_mysql.c: At top level:
_mysql.c:647: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c: In function ‘_mysql_ConnectionObject_clear’:
_mysql.c:679: error: ‘_mysql_ConnectionObject’ has no member named ‘converter’
_mysql.c:680: error: ‘_mysql_ConnectionObject’ has no member named ‘converter’
_mysql.c:680: error: ‘NULL’ undeclared (first use in this function)
_mysql.c:680: warning: statement with no effect
_mysql.c: At top level:
_mysql.c:687: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:715: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:731: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:749: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:768: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:794: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:816: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:848: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:874: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:901: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:916: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:933: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:949: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:967: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1002: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1033: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1035: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1065: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1095: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1129: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1161: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1197: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1221: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1246: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1271: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1310: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1349: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1354: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c:1357: error: expected declaration specifiers or ‘…’ before ‘_PYFUNC’
_mysql.c: In function ‘_mysql__fetch_row’:
_mysql.c:1363: error: ‘PyObject’ undeclared (first use in this function)
_mysql.c:1363: error: ‘v’ undeclared (first use in this function)
_mysql.c:1363: error: invalid operands to binary *
_mysql.c:1363: warning: statement with no effect
_mysql.c:1364: error: ‘_mysql_ResultObject’ has no member named ‘use’
_mysql.c:1365: error: ‘_mysql_ResultObject’ has no member named ‘result’
_mysql.c:1365: warning: passing argument 1 of ‘mysql_fetch_row’ from incompatible pointer type
_mysql.c:1367: error: ‘Py_BEGIN_ALLOW_THREADS’ undeclared (first use in this function)
_mysql.c:1367: warning: statement with no effect
_mysql.c:1368: error: ‘_mysql_ResultObject’ has no member named ‘result’
_mysql.c:1368: warning: passing argument 1 of ‘mysql_fetch_row’ from incompatible pointer type
_mysql.c:1369: error: ‘Py_END_ALLOW_THREADS’ undeclared (first use in this function)
_mysql.c:1369: warning: statement with no effect
_mysql.c:1371: error: ‘_mysql_ResultObject’ has no member named ‘conn’
_mysql.c:1371: error: ‘_mysql_ConnectionObject’ has no member named ‘connection’
_mysql.c:1371: warning: passing argument 1 of ‘mysql_errno’ from incompatible pointer type
_mysql.c:1372: error: ‘_mysql_ResultObject’ has no member named ‘conn’
_mysql.c:1376: warning: implicit declaration of function ‘_PyTuple_Resize’
_mysql.c:1376: error: ‘r’ undeclared (first use in this function)
_mysql.c:1379: warning: implicit declaration of function ‘convert_row’
_mysql.c:1379: warning: statement with no effect
_mysql.c: At top level:
_mysql.c:1397: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1476: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1504: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1526: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1566: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1595: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1610: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1625: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1640: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1656: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1691: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1709: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1732: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1749: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1765: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1794: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1817: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1847: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1869: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1896: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1917: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1958: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:1978: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c: In function ‘_mysql_ConnectionObject_dealloc’:
_mysql.c:2012: error: ‘PyObject’ undeclared (first use in this function)
_mysql.c:2012: error: ‘o’ undeclared (first use in this function)
_mysql.c:2012: error: invalid operands to binary *
_mysql.c:2012: warning: statement with no effect
_mysql.c:2015: error: ‘_mysql_ConnectionObject’ has no member named ‘open’
_mysql.c:2016: warning: implicit declaration of function ‘_mysql_ConnectionObject_close’
_mysql.c:2016: error: ‘NULL’ undeclared (first use in this function)
_mysql.c:2016: warning: statement with no effect
_mysql.c:2019: warning: implicit declaration of function ‘PyMem_Free’
_mysql.c: At top level:
_mysql.c:2022: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2039: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2054: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2076: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c: In function ‘_mysql_ResultObject_dealloc’:
_mysql.c:2098: error: ‘_mysql_ResultObject’ has no member named ‘result’
_mysql.c:2098: warning: passing argument 1 of ‘mysql_free_result’ from incompatible pointer type
_mysql.c: At top level:
_mysql.c:2103: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2113: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ConnectionObject_methods’
_mysql.c:2328: error: array type has incomplete element type
_mysql.c:2329: error: ‘T_INT’ undeclared here (not in a function)
_mysql.c:2329: warning: implicit declaration of function ‘offsetof’
_mysql.c:2329: error: expected expression before ‘_mysql_ConnectionObject’
_mysql.c:2329: error: ‘RO’ undeclared here (not in a function)
_mysql.c:2336: error: ‘T_OBJECT’ undeclared here (not in a function)
_mysql.c:2336: error: expected expression before ‘_mysql_ConnectionObject’
_mysql.c:2343: error: ‘T_UINT’ undeclared here (not in a function)
_mysql.c:2343: error: expected expression before ‘_mysql_ConnectionObject’
_mysql.c:2350: error: expected expression before ‘_mysql_ConnectionObject’
_mysql.c:2357: error: expected expression before ‘_mysql_ConnectionObject’
_mysql.c:2364: error: ‘NULL’ undeclared here (not in a function)
_mysql.c:2367: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ResultObject_methods’
_mysql.c:2419: error: array type has incomplete element type
_mysql.c:2420: error: expected expression before ‘_mysql_ResultObject’
_mysql.c:2430: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2458: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2488: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c: In function ‘_mysql_ConnectionObject_setattr’:
_mysql.c:2490: error: ‘v’ undeclared (first use in this function)
_mysql.c:2491: warning: implicit declaration of function ‘PyErr_SetString’
_mysql.c:2491: error: ‘PyExc_AttributeError’ undeclared (first use in this function)
_mysql.c:2496: warning: implicit declaration of function ‘PyMember_Set’
_mysql.c: At top level:
_mysql.c:2513: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c: In function ‘_mysql_ResultObject_setattr’:
_mysql.c:2515: error: ‘v’ undeclared (first use in this function)
_mysql.c:2516: error: ‘PyExc_AttributeError’ undeclared (first use in this function)
_mysql.c: At top level:
_mysql.c:2534: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ConnectionObject_Type’
_mysql.c:2618: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ResultObject_Type’
_mysql.c:2704: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_methods’
_mysql.c:2776: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2808: warning: return type defaults to ‘int’
_mysql.c: In function ‘DL_EXPORT’:
_mysql.c:2808: error: expected declaration specifiers before ‘init_mysql’
_mysql.c:2886: error: expected ‘{’ at end of input
error: command ‘gcc’ failed with exit status 1
aldo on 17 Jun 2009 at 12:07 am #
very great tutorial! thanks!
raghava on 19 Jun 2009 at 6:59 am #
I have centos 4.7(final), python 2.3.4, and i am trying to install the trac 0.11.4, while configured every thing i got this error on the browser window. can any body help me……
Traceback (most recent call last):
File "/usr/lib/python2.3/site-packages/Trac-0.11.4-py2.3.egg/trac/web/api.py", line 367, in send_error
‘text/html’)
.
.
File "/usr/lib/python2.3/site-packages/Trac-0.11.4-py2.3.egg/trac/db/api.py", line 111, in _parse_db_str
scheme, rest = db_str.split(’:', 1)
ValueError: unpack list of wrong size
raghava.
Lionel on 08 Jul 2009 at 10:13 pm #
Hi,
Thanks for your tutorial, I have a small problem I installed both svn and trac, but when i go to localhost/trac if i set my repo to /var/www/svn/myproject it will keep asking me for a password, if i put it to my trac it will of course tell me that the path is not a svn repo.
any idea?
Thanks
cubanitoweb on 30 Aug 2009 at 1:42 am #
Please, help me. My english is no good.
I am new on CentOS and Iam trying to install trac on CentOS 5 web server.
At your step-by-step guide, in
python setup.py build && python setup.py install
I get an error:
Traceback (most recent call last):
File "setup.py", line 5, in ?
from setuptools import setup, Extension
ImportError: No module named setuptools
Can you help me?
Thanks
Bren on 04 Sep 2009 at 6:27 am #
cubanitoweb, I had the same problem; This worked for me:
1) Download setuptools appropriate for your Python installation version:
e.g.: Mine was 2.4:
wget http://pypi.python.org/packages/2.4/s/setuptools/setuptools-0.6c9-py2.4.egg#md5=260a2be2e5388d66bdaee06abec6342a
2) Install via ssh
e.g.:
sh setuptools-0.6c9-py2.4.egg
Danijel on 11 Sep 2009 at 12:35 am #
Dawson,
I get the same error as you while trying to build mysql-devel.
"…
.
.
.
_mysql.c:2491: error: ‘PyExc_AttributeError’ undeclared (first use in this function)
_mysql.c:2496: warning: implicit declaration of function ‘PyMember_Set’
_mysql.c: At top level:
_mysql.c:2513: error: expected declaration specifiers or ‘…’ before ‘PyObject’
_mysql.c: In function ‘_mysql_ResultObject_setattr’:
_mysql.c:2515: error: ‘v’ undeclared (first use in this function)
_mysql.c:2516: error: ‘PyExc_AttributeError’ undeclared (first use in this function)
_mysql.c: At top level:
_mysql.c:2534: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ConnectionObject_Type’
_mysql.c:2618: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_ResultObject_Type’
_mysql.c:2704: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘_mysql_methods’
_mysql.c:2776: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token
_mysql.c:2808: warning: return type defaults to ‘int’
_mysql.c: In function ‘DL_EXPORT’:
_mysql.c:2808: error: expected declaration specifiers before ‘init_mysql’
_mysql.c:2886: error: expected ‘{’ at end of input
error: command ‘gcc’ failed with exit status 1″
I hope someone helps soon with this…
Danijel on 17 Sep 2009 at 2:09 am #
I just upgraded my CentOS from 5.2 to 5.3… Didn’t help.
endris on 22 Sep 2009 at 7:05 am #
Works just fine !
But exists two pitfalls:
1. PythonHandler trac.web.mod python_frontend
change to:
PythonInterpreter main_interpreter
PythonHandler trac.web.modpython_frontend
2. Don’t forget to give read/write permissions to $pathtoyourtracproject
Giedrius on 10 Jan 2010 at 3:35 am #
Accessing the TRAC URL was giving a 500 Internal Server Error and complaining in the log about being unable to load Genshi.
Solution? Disable SELinux.
Alternatives?
I am trying to install in Centos: 5.4
Please, help
Michael on 11 Jan 2010 at 6:42 am #
No need to compile MySQL-python. It’s in repo already.
Just run yum -y install Install MySQL-python
And thanks in advance for manual!!!