[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lynx-dev] Installation error for Lynx on Linux
From: |
Gajanan Polaswar |
Subject: |
Re: [Lynx-dev] Installation error for Lynx on Linux |
Date: |
Thu, 20 Sep 2012 10:07:05 +0000 |
Thanks Thomas,
We have solved issue with some environmental issue
Thanks and Regards
Gajanan B. Polaswar | Senior Team Lead
address@hidden | Cell: +91-9822391296 | Tel: +91-20-67036170
Persistent Systems Ltd. | 20 Glorious Years | www.persistentsys.com
-----Original Message-----
From: Thomas Dickey [mailto:address@hidden
Sent: Wednesday, September 19, 2012 5:34 AM
To: Gajanan Polaswar
Cc: address@hidden; ibm_spss_hana
Subject: Re: [Lynx-dev] Installation error for Lynx on Linux
On Tue, Sep 18, 2012 at 11:41:04AM +0000, Gajanan Polaswar wrote:
> Hi,
>
> We are trying to install Lynx on Linux Red hat 64 ES5.
> Followed below step to Configure and install lynx 1. Extracted gzip -d
> lynx2.8.7.tar.gz to root directory 2. Then executed following command
> in sequence in the extracted folder.
> ./configure -with-ssl
./configure --with-ssl
Some detail is missing, but the -I/usr/kerberos/include sounds like a broken
configuration which appeared first in Fedora. I used to work around this as
indicated in this note:
rh90's openssl relies on /usr/kerberos (should I add to configure?)
#!/bin/sh
KRB=/usr/kerberos
export LIBS="-L$KRB/lib -lssl -lcrypto -lgssapi_krb5 -lkrb5 -lk5crypto
-lcom_err"
export CPPFLAGS="-I$KRB/include -I/usr/include/openssl"
export CFLAGS="-O -g $CPPFLAGS"
cfg-lynx $*
Later I found that the pkg-config script almost worked, and last changed the
configure script to work around _that_ in 2.8.8dev.3:
2010-04-25 (2.8.8dev.3)
* add workaround in CF_SSL configure macro for broken openssl pkg-config script
on Redhat, CentOS -TD
(2.8.8dev.14 is current - a small number of bugs/improvements have been
reported against that)
--
Thomas E. Dickey <address@hidden> http://invisible-island.net
ftp://invisible-island.net
DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the
property of Persistent Systems Ltd. It is intended only for the use of the
individual or entity to which it is addressed. If you are not the intended
recipient, you are not authorized to read, retain, copy, print, distribute or
use this message. If you have received this communication in error, please
notify the sender and delete all copies of this message. Persistent Systems
Ltd. does not accept any liability for virus infected mails.