freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Plot Lost <plot.lost AT gmail.com>
- To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] Can't compile with OpenSSL
- Date: Sun, 3 Oct 2010 19:41:58 +0400
>
>
>
>
> Ok, stop, right here. Look at the paths - are they accurate to your
> installation of OpenSSL? On my system (Slackware), those paths are
> incorrect. I'm referring specifically to the -I/usr/local/ssl/include and
> the -L/usr/local/ssl/lib parameters. I don't have the source in front of me
> at the moment, but I would guess that you need to actually specify
> --with-openssl=/base/ssl/path (i.e. /usr ).
>
>
Those are the right paths for this system, other code such as apache httpd
compile fine against that.
> ../../replacements/.libs/libreplacements.a -lssl -lcrypto -lrt
>> ../../dblib/.libs/libsybdb.so: undefined reference to `dlsym'
>> ../../dblib/.libs/libsybdb.so: undefined reference to `dlerror'
>> ../../dblib/.libs/libsybdb.so: undefined reference to `dladdr'
>> ../../dblib/.libs/libsybdb.so: undefined reference to `dlopen'
>> ../../dblib/.libs/libsybdb.so: undefined reference to `dlclose'
>> collect2: ld returned 1 exit status
>>
>
> The alternative issue that you might be having is with it properly locating
> libdl.
>
> Ah, that's solved it - jogged my memory about a similar problem I had with
curl.
Got it fixed by configuring as follows:
env LDFLAGS="-ldl" ./configure --with-ssl
Then it compiles fine.
Thanks for the help with this.
-
[freetds] Can't compile with OpenSSL,
Plot Lost, 10/03/2010
-
Re: [freetds] Can't compile with OpenSSL,
I put the Who? in Mishehu, 10/03/2010
- Re: [freetds] Can't compile with OpenSSL, Plot Lost, 10/03/2010
-
Re: [freetds] Can't compile with OpenSSL,
I put the Who? in Mishehu, 10/03/2010
Archive powered by MHonArc 2.6.24.