FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Daniel Morgan [mailto:danmorg AT sc.rr.com]
> Sent: October 15, 2002 3:40 PM
> 
> I checked out from cvs freetds and compiled on cygwin.  This 
> is the build
> error i got.  It appears I do not have ksh installed.  ksh is the korn
> shell, right?  It does not come with cygwin.  Anyways, I'm 
> sure I can modify the make file to bypass the docs.
> 
> Making all in doc
> make[1]: Entering directory `/home/DanielMorgan/freetds/doc'
> ./txt2man -P FreeTDS -t FreeTDS -r 0.60 ./freebcp.txt >freebcp.1
> exec: ksh: not found
> make[1]: *** [freebcp.1] Error 127
> make[1]: Leaving directory `/home/DanielMorgan/freetds/doc'
> make: *** [all-recursive] Error 1

What a day on the FreeTDS list!  

Yes, after a couple of tries, as you found out, txt2man won't be invoked.
Not because it gets bored or anything, it just stupidly creates empty man
pages and doesn't rebuild them unless you change their sources.  Thanks for
mentioning this.  

I'm going to remove txt2man from our cvs and change the doc/Makefile such
that it doesn't build man pages unless `which txt2man` returns a positive
result.  That way, he who will build the docs will find out he needs certain
freely available tools, and anyone else won't trip on them.  

OT, there is a ksh in the public domain, and David Korn managed to get his
employer to release the real thing under an open source license.  I don't
even know whether txt2man really needs ksh.  

> Shouldn't cygsybdb-2.dll be sybdb.dll or libsybdb.dll?

Now that it's not impossible, you don't like the names?  Seriously, how do
you arrive at what they "should" be?  Probably if anything they should be
whatever Microsoft or Sybase would call them.  Or whatever you'd call them?


btw, does it produce import libraries too?  

Regards, 

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.