[freetds] installation
Matt Davies
tonmatt at gmail.com
Mon Dec 4 07:16:09 EST 2006
OK
I did do
aclocal
automake
then the make command worked, and the make install worked.
I then installed pymssql, no error messages.
then in python
>>>import pymssql
errors
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "pymssql.py", line 30, in ?
import _mssql
ImportError: libsybdb.so.5: cannot open shared object file: No such file or
directory
find / -name "ibsybdb.so.5" -print
Made symoblic link in /usr/lib to point at that file and now import pymssql
works fine
On 03/12/06, Matt Davies <tonmatt at gmail.com> wrote:
>
> I've got that workign fine on that box using the sample script here
>
> http://b3d70.blogspot.com/2006/04/pymssql-example-script.html
>
> Now on the box where I actually need to get it working I'm getting a
> different error.
>
> Heres the details
>
> Python 2.4.3 (#1, Jun 13 2006, 11:46:08)
> [GCC 4.1.1 20060525 (Red Hat 4.1.1-1)] on linux2
>
> ./configure --enable-msdblib
>
> this runs fine
>
> make
> cd . && /bin/sh /usr/src/freetds- 0.1/missing --run automake-1.9 --gnu
> Makefile
> configure.in:18: version mismatch. This is Automake 1.9.6,
> configure.in:18: but the definition used by this AM_INIT_AUTOMAKE
> configure.in:18: comes from Automake 1.9.5. You should recreate
> configure.in:18: aclocal.m4 with aclocal and run automake again.
> make: *** [ Makefile.in] Error 1
>
> I'm pretty sure I need to recreate aclocal.m4 with aclocal and then run
> automake again. But will this have any impact on the current installs of
> python and the rest of the software running?
>
> it's a live machine, so I'm a bit worried.
>
> Although it seems like I"ll just be telling the install procedure to use
> an older version of itself for one install, and I suppose I can switch it
> back to the new version after the install??
>
> Getting there
>
> I only seem to be getting one email per day, I wanted to get them as live,
> does anyone know what I need to change in my settings for the mailing list?
>
>
>
> On 03/12/06, Matt Davies <tonmatt at gmail.com> wrote:
> >
> > I can see that this might be easier if I was on a Linux box. So, James,
> > I'll take your advice and I'm now on one of my FC4 installs, through
> > terminal.
> >
> > I'll go through the process again and list it here, I might well work it
> > out for myself like this, but I'll still post anyway, in case it helps
> > anyone.
> >
> > here's the machines details when you go into the python
> > Python 2.4.3 (#1, Jun 13 2006, 16:41:18)
> > [GCC 4.0.2 20051125 (Red Hat 4.0.2-8)] on linux2
> >
> > as root
> >
> > cd /usr/src/freetds-0.1
> > ./configure --enable-msdblib
> > make
> > make install
> > cd ../pymssql-0.8.0/
> > python setup.py install
> >
> > I got no erros then, woohoo!!
> >
> > And now in the python shell
> >
> > >>> import pymssql
> >
> > Doesn't give me an error
> >
> > thanks everyone, I'll just do the pretty stuff on the mac then, and the
> > grungy stuff on the linux boxes from now on :-)
> >
> >
> >
> >
> >
> > On 02/12/06, James K. Lowden <jklowden at freetds.org> wrote:
> > >
> > > Daniel Fazekas wrote:
> > > > If you really want a Universal copy of FreeTDS, it's going to get a
> > > > little more involved, as unfortunately the FreeTDS build system
> > > isn't
> > > > really set up to handle building for multiple architecture
> > > > simultaneously
> > >
> > > Hi Daniel,
> > >
> > > I have a vague recollection that one important step -- necessary but
> > > insufficient IIRC -- is upgrading the autotools, specifically
> > > libtool. Is
> > > that your understanding, too.
> > >
> > > I write this using my Powerbook, which is a very comfortable way to
> > > use
> > > NetBSD via remote X. But I'm not really tempted to develop on it or
> > > for
> > > it.
> > >
> > > Regards,
> > >
> > > --jkl
> > > _______________________________________________
> > > FreeTDS mailing list
> > > FreeTDS at lists.ibiblio.org
> > > http://lists.ibiblio.org/mailman/listinfo/freetds
> > >
> >
> >
>
More information about the FreeTDS
mailing list