Skip to Content.
Sympa Menu

freetds - Re: Compiling under Redhat Linux

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Kevin Wormington" <kworm AT sofnet.com>
  • To: "TDS Development Group" <freetds AT franklin.oit.unc.edu>
  • Subject: Re: Compiling under Redhat Linux
  • Date: Thu, 26 Aug 1999 17:32:33 -0500


-----Original Message-----
From: Michael Peppler <mpeppler AT peppler.org>
To: TDS Development Group <freetds AT franklin.oit.unc.edu>
Date: Thursday, August 26, 1999 5:53 PM
Subject: [freetds] Re: Compiling under Redhat Linux


>Brian Bruns writes:
> >
> >
> > On Thu, 26 Aug 1999, Michael Peppler wrote:
> >
> > > Brian Bruns writes:
> > > >
> > > >
> > > > On Thu, 26 Aug 1999, Michael Peppler wrote:
> > > >
> > > > > Kevin Wormington writes:
> > > > > > Hi all, I have been trying to compile the snapshot version
under Redhat
> > > > > > Linux 5.2 and I get a slew of errors regarding "@SHELL@" and
"@LIBTOOL@" not
> > > > > > being found. I know that I could modify the Makefile.in to
point to the
> > > > > > correct path, but am I missing something to set the paths in a
single place?
> > > > > >
> > > > >
> > > > > I had the same problem this morning.
> > > > >
> > > > > I ended up reinstalling autoconf and libtool from the sources...
> > > > >
> > > > > Michael
> > > >
> > > > Did that end up working for you? I only need to install libtool and
> > > > everything was happy (actually I only needed the m4 file but...)
> > >
> > > I first did that, but I may have gotten a libtool that was too recent,
> > > because one of the commands then complained that I needed autoconf
> > > 2.13 instead of 2.12. So I ended up getting the new autoconf, and
> > > installing that (which was quick).
> > >
> > > After that things went fine.
> > >
> > > What I'm not sure I understand is why the autoconf package is needed
> > > at all. I don't have any of that installed on my Sun box and the build
> > > doesn't break there...
> > >
> > Yeah, if you don't have aclocal/autoconf/etc... it skips trying to
rebuild
> > configure and uses the one that comes with the package. If you have
> > autoconf then it tries to use it. I'm not sure whether that is standard
> > autoconf behaviour or whether the guy that gnuified freetds put that in.
>
>That's sorta weird. I would have thought that you'd only rebuild
>configure when you build the package (ie make a new distribution), but
>when you distribute the package you use the configure that comes with
>the package. Otherwise you're bound to get the sort of problems that
>we see on RH5.2 where the autoconf package is broken.
>
>At least that seems to be the right way to do it in my humble opinion
>:-)
>
>Michael


I would agree, with most other packages you just run configure and make, it
doesn't try to regenerate everything.

Kevin





Archive powered by MHonArc 2.6.24.

Top of Page