[Trac] Trying to install Trac on Centos 4.1 x86_64

[Giulio Cesare Solaroli]

Hi Viren,

here the output of the file command:
[root at ultra ~]# file /usr/lib/python2.3/site-packages/neo_cgi.so
/usr/lib/python2.3/site-packages/neo_cgi.so: ELF 32-bit LSB shared
object, Intel 80386, version 1 (SYSV), not stripped

while

[root at ultra ~]# file /usr/bin/python2.3
/usr/bin/python2.3: ELF 64-bit LSB executable, AMD x86-64, version 1
(SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs),
stripped

If I understand this right, I have the 64-bit version of python, while
the neo_cgi is a 32 bit version.

I suppose the best way to fix this is to find/recompile the
clearsilver module for the x86_64 architecture, isn't it?

Regards,

Giulio Cesare



On 10/3/05, Viren Shah <vshah at virtc.com> wrote:
>
> Can you do a "file /usr/lib/python2.3/site-packages/neo_cgi.so" and see
> what that reports back?
> I'm wondering if the 32-bit vs. 64-bit issue is biting you.
> Viren
>
> Giulio Cesare Solaroli wrote:
> > Hi everybody,
> >
> > I have just joined this mailing list because I am having some problems
> > in installing Trac on my new development machine (Sun Ultra20 running
> > Centos 4.1/x86_64)
> >
> > I have tried to search on the list archive, but I have not been able
> > to find anything relevant to my problem. I am not sure of what is
> > causing the problem, so I may have looked at it the wrong way.
> >
> > I have followed many different paths till now (trying to clean the
> > outcome of every test as completely as possible, in order not to alter
> > the following ones), from searching for RPMs to compiling straight
> > from the sources.
> >
> > Untill now, I have achieved the best outcome using the following RMPs:
> > - clearsilver-0.9.13-1.2.el4.rf.i386.rpm
> > - python-clearsilver-0.9.13-1.2.el4.rf.i386.rpm
> > - trac-0.8.4-1.2.el4.rf.noarch.rpm
> >
> > The first two RPMs are for i386, instead of x86_64, but I have not
> > been able to find anything better.
> >
> > After doing all the preliminary configurations, trying to access the
> > starting url (http://ultra/cgi-bin/trac.cgi), I get the following
> > message:
> >
> >
> >>Oops...
> >>
> >>Trac detected an internal error:
> >>
> >>/usr/lib/python2.3/site-packages/neo_cgi.so: cannot open shared
> >
> > object file: No such file or directory
> >
> >>Traceback (most recent call last):
> >> File "/var/www/cgi-bin/trac.cgi", line 25, in ?
> >>   trac.core.cgi_start()
> >> File "/usr/lib/python2.3/site-packages/trac/core.py", line 533, in cgi_start
> >>   send_pretty_error(e, None)
> >> File "/usr/lib/python2.3/site-packages/trac/core.py", line 473, in send_pretty_error
> >>   req.init_request()
> >> File "/usr/lib/python2.3/site-packages/trac/core.py", line 341, in init_request
> >>   Request.init_request(self)
> >> File "/usr/lib/python2.3/site-packages/trac/core.py", line 272, in init_request
> >>   import neo_cgi
> >>ImportError: /usr/lib/python2.3/site-packages/neo_cgi.so: cannot open
> >
> > shared object file: No such file or directory
> >
> >
> >
> > The required file is (obviously) in the right place:
> >
> >
> >>[root at ultra ~]# ls -al /usr/lib/python2.3/site-packages/
> >>total 840
> >>drwxr-xr-x  11 root root   4096 Oct  2 04:00 .
> >>drwxr-xr-x   3 root root   4096 Sep 30 01:12 ..
> >>[...]
> >>-rwxr-xr-x   1 root root 241350 Feb 16  2005 neo_cgi.so
> >>[...]
> >
> >
> >
> > What could be wrong, given the above error, in my setup?
> > Any insight on how to move forward would be welcome.
> >
> > Thank for you attention.
> >
> > Best regards,
> >
> > Giulio Cesare Solaroli
> > _______________________________________________
> > Trac mailing list
> > Trac at lists.edgewall.com
> > http://lists.edgewall.com/mailman/listinfo/trac
> >
> >
> >
>
>
> --
> Viren R Shah
> Sr. Technical Advisor
> Virtual Technology Corporation
> vshah at virtc.com
> P: 703-333-6246
>
>