FreeTDS Development Group

[RWilbert AT exchange.webmd.net]

I will. 

As a side note with 0.60 I noticed another anomaly that don't know if anyone
else has seen.

Also let me say that I have install configured freetds successfully on Linux
many times (I just didn't want you to think I was a total loser   ;) ).

On RedHat 8.0 DBD::Sybase(0.91) does some weird things with freetds 0.60. I
will only look at the interface entry if you use a
interface="[freetds.conf:entry]". Which is not normal because that is used
specify an non-default interfaces file. I will reference the freetds.conf
entry and pull the port and tds version but will not grab the server info.
It pulls an IP on aol's network (172.192.172.136) where the server entry for
the freetds.conf is :
host = 172.21.1.131.

If you use the "server=[freetds.conf:entry]" argument in the connect
statement it will try to resolve that entry name via dns and connect via
port 0.

This is why  tried  rolling back to .53 and it was a perfect install on
RedHat8.0(just to restore my sanity);

But since I only use DBD::Sybase with Freetds it may just be an issue with
DBD::Sybase-0.91 and freetds-0.60 (?).


-----Original Message-----
From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
Sent: Thursday, October 31, 2002 5:36 PM
To: TDS Development Group
Subject: [freetds] RE: Shared libraries not installing on AIX


> From: RWilbert AT exchange.webmd.net [mailto:RWilbert AT exchange.webmd.net]
> Sent: October 31, 2002 5:03 PM
>
> I just did a:
> ./configure --prefix=/usr/local/freetds --with-tdsver=7.0 and 
> I have the same problem. 

ie, no error and no shared libraries, right?  I may have to list this under
"known issues".  

> I dl freetds-0.53 and during the ./configure 
> (same as above) I
> got:
> *** Warning: the GNU linker, at least up to release 2.9.1, is reported
> *** to be unable to reliably create shared libraries on AIX.
> *** Therefore, libtool is disabling shared libraries support.  If you
> *** really care for shared libraries, you may want to modify your PATH
> *** so that a non-GNU linker is found, and then restart.
> 
> Pretty Cool message huh ?
> I did'nt know there was a issue with gcc and AIX but that 
> looks like that is my problem.

Don't get me don't get me don't get me started on libtool.  Gadzooks is it a
pain.  

I have to agree that message is clear, give 'em credit for that.  Now, try
to find out the current state of affairs, try to find out if this is thought
to be solved and if so as of what version.  Don't be surprised if you come
home emptyhanded though.  :(

FWIW, I have: $ ld --version
                GNU ld 2.11.2

What I don't understand and doubt I can find out is: What to do?  I mean, I
suppose if you point your path to AIX's ld, that might help.  But if it
does, what happened to the warning?  (The 0.53 release used older versions
of the GNU autotools to generate the configure script than we're using now.
You're using the 0.60 release, yes?  That might -- I don't know -- have used
*older* tools than 0.53 did; they were built by different people on
different machines with different OS's.  That could account for the missing
warning, but who can tell?)  And if it doesn't, then what?  

Roger, if you haven't already, please try the latest snapshot.  If that
doesn't solve the problem, I'd like very much to know.  Even though I, um,
don't like libtroll ^W libtool very much, I have to document anything that
our AIX friends might trip over.  

It would help if you would use script(1) to capture the whole output of
"configure; make; make install" and post the file (as an attachment) here.
That way we can check for messages and look at precisely what "make" is
doing.  

Thanks for your time.  

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



---
You are currently subscribed to freetds as: [rogerw AT webmd.net]
To unsubscribe, forward this message to
$subst('Email.Unsub')