Skip to Content.
Sympa Menu

freetds - RE: [freetds] Error building nightly snapshot

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Error building nightly snapshot
  • Date: Tue, 2 Dec 2003 17:11:39 -0500

> From: James McGowan [mailto:jmcgowan AT luxurylink.com]
> Sent: December 2, 2003 4:30 PM
>
> Following the advice of other members, I tried building the
> lastest nightly snapshot and got this error:
>
> creating libtds.la
> (cd .libs && rm -f libtds.la && ln -s ../libtds.la libtds.la)
> make[3]: *** No rule to make target
> `sybase_character_sets.h.pl', needed by
> `sybase_character_sets.h'. Stop.

Argh. Try:

$ touch -t 190001010101 src/tds/sybase_character_sets.h.pl

or anything else that creates a sybase_character_sets.h.pl older than
sybase_character_sets.h.

We developers generate sybase_character_sets.h from
sybase_character_sets.h.pl, but we don't expect a configure script to do
that. As a convenience (and documentation) we recently added that .h.pl ->
.h rule, but I guess you're the first fellow to use the result who isn't
using CVS (CVS users would have the .pl file).

Freddy: I don't want to include sybase_character_sets.h.pl in the
distribution, because it should never be needed. I don't want to start any
rumors about needing Perl to run our configure script. If we want to leave
this rule in our makefile, that's OK, but it should have no effect unless
explicitly enabled.

I'll try to fix this in time for tonight's snapshot.

--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 we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page