Skip to Content.
Sympa Menu

freetds - RE: Problem building freetds --- gcc location

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: Problem building freetds --- gcc location
  • Date: Mon, 28 Oct 2002 17:09:50 -0500


> From: Kanneboina, Venkat [mailto:VenkatKanneboina AT ca.slr.com]
> Sent: October 28, 2002 4:37 PM
>
> I have tried with setting CC=/usr/local/bin/gcc , it did not work.
> As advised, I have given a portion of the output of the configure command
here:
>
> Script started on Mon Oct 28 13:16:29 2002
> # ./configure --prefix=/mis2/freetds-0.60 --with-tdsver=7.0
--enable-msdblib^M
> [...]
> checking for working makeinfo... missing^M
> checking for gcc... (cached) cc^M
^^^^^^
Thanks, Venkat, that's very clear. Please delete config.cache, make sure CC
is exported, and try again.

I don't know why configure picked up a different CC the first time. It
might be that you've been relying on the cache ever since.

Nick, did we intentionally stop creating cache files, or did they stop being
created by default with the new autoconf? I used to always get a
config.cache, but no more. "info autoconf" says there's no cache file by
default for autoconf 2.54.

Venkat, if it's not too much trouble, please send list mail in plain text
(not html), as a courtesy to everyone. And there's no need to cc me; I read
the list. ;)

Let us hear the good news. :-)

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