FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

blackwater dev wrote:
> On 4/11/07, James K. Lowden <jklowden AT freetds.org> wrote:
> >
> > blackwater dev wrote:
> > > I'm currently moving my site to a site hosted by dreamhost and am
> > > having problems installing freetds.
> > >
> > > I installed it to my home directory but get this error after the
> > > make.
> > >
> > > make[1]: Entering directory
> > > `/home/.minnie/blackwaterdev/freetds-0.64/doc' ./txt2man -I 'FreeTDS
> > > User Guide'  -v 'FreeTDS Utilities' -t FreeTDS -r 0.64./freebcp.txt
> > > >.freebcp.1
> > > /bin/sh: line 1: ./txt2man: No such file or directory
> > > make[1]: *** [freebcp.1] Error 127
> >
> > Another option is to "touch freebcp.1" (and so on), telling make(1)
> > not to build them.  The overall build would then work, and you could
> > copy the man pages, should you so desire, to your dreamhost server.
>
> I'm a linux newb and can do the ./configure, make, make install, etc. 
> Not sure exactly what you mean by touch.

I meant the "touch" command, cf. touch(1) in your manual.  It's a way to
set the date information on a file, but it's also the most popular way to
create a new empty file.  

make(1) for some reason is trying to *build* the man page (freebpc.1).  It
doesn't need to, because freebcp.1 is included in the distribution.  That
leads me to think something else is wrong. 

You could fool make(1) into thinking the pages were already built: if you
"touch /home/.minnie/blackwaterdev/freetds-0.64/doc/freebcp.1", and then
"make" again, it will see the file is already built and go on to the next
step.  

As I said though, freebcp.1 should be in the doc directory as soon as you
run tar, before you even run configure.  If it's not, something is wrong,
either a corrupted tarball or (unlikely) a broken tar program.  Or
soemthing else, of course.  Never rule out something else.  

HTH.  

--jkl