Thanks to Malcolm and Srdjan for your replies.
Don't get me wrong, Malcolm, I'm not knocking Django! far from it, I
think it's the bees knees.
It looks like what I've actually got here is a problem caused by a
mixture of i386 and x86_64 libraries.
if I try to build mysql-devel, the build appear
I had the same situation as my server is CentOS 5.2. Django needed
MySQL-python 1.2.2. I tried Yum but the default repo gave me version
1.2.1.
You can find version 1.2.2 at SourceForge, but to install it you need
to have MySQL development tools installed on your server. The package
is called "mys
On Mon, 2008-12-15 at 11:40 +, Rachel Willmer wrote:
> Thanks for the reply.
>
> Unfortunately the egg gives me the same problems as when I attempt an
> install from the tarball.
>
> Any RHEL users out there encountered this problem and fixed it?
Whilst I use similar vintage RHEL boxes wit
Thanks for the reply.
Unfortunately the egg gives me the same problems as when I attempt an
install from the tarball.
Any RHEL users out there encountered this problem and fixed it?
Rachel
--~--~-~--~~~---~--~~
You received this message because you are subscribe
It should work if you install the egg.
J
2008/12/12 Rachel Willmer :
>
> I'm installing Django on a customer's machine which is running Red Hat
> Enterprise Linux Server release 5.2.
>
> Django 1.0 complains about the version of mysql-python available,
> which is 1.2.1-1, where it needs 1.2.1p2.
I'm installing Django on a customer's machine which is running Red Hat
Enterprise Linux Server release 5.2.
Django 1.0 complains about the version of mysql-python available,
which is 1.2.1-1, where it needs 1.2.1p2.
Trying to install the latest tarball from sourceforge gives me lots of
other fil
6 matches
Mail list logo
