Skip to Content.
Sympa Menu

freetds - RE: Corrupt file 0.60rc1

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: Corrupt file 0.60rc1
  • Date: Tue, 10 Sep 2002 12:36:33 -0400


> I'm about to post rc4, trying to combine your ideas and
> Brian's. Basically,
> rc3 was a tarball of the whole CVS tree. I downloaded it
> here, did "make
> dist" (using gnu make), and added the README.0.60. It needs
> a note about tds8.

OK, I just did that. I've had my coffee and enough sleep, and now I know
something's up.

"make dist" on my machine, even ensuring I'm using Gnu make, creates a
tarball whose src/odbc directory is empty except for a unittests directory
and a zero-length Makefile.

I agree with Frediano that "make dist" ought to be how distributions are
made. I realize that's radical and everything, but, you know, we've all got
our convictions.

I'll allow that it may be the case that NetBSD won't "make dist" correctly,
but I don't file that under Good Thing. I'm going to look into
autogen.sh....

--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.






Archive powered by MHonArc 2.6.24.

Top of Page