[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] urg: looking for statically linked binary of lynx, please

From: Thomas Dickey
Subject: Re: [Lynx-dev] urg: looking for statically linked binary of lynx, please help!
Date: Wed, 21 Jan 2009 06:05:45 -0500 (EST)

On Wed, 21 Jan 2009, Y P wrote:

Thanx anyway,
will look after other static bins (elinks, links2).

It's likely the be the same problem (unless you happen to meet up with the
rare individual who's built a static binary for some embedded app).

On the other hand, since you didn't respond to any of the questions about
compiling it yourself, that's still a possibility.

On Mon, Jan 19, 2009 at 10:38:07PM +0000, David Woolley wrote:
Y P wrote:

On Fri, Jan 16, 2009 at 08:07:49AM +0000, David Woolley wrote:
Seems to me that you can use a dynamically linked version, as long as
you have an appropriate LDLIBRARYPATH.

I don't know ! I'm webmaster, not the server-admin. I don't know so much
about rpm-based sysstems, I don't use such myself at home.

LDLIBRARYPATH has nothing to do with RPMs.  Its fundamental to Unix
shared libraries.

Even if there wwe some reason
why you couldn't have shared objects, you could static link private
libraries and dynamic link system ones.

The system doesn't authorizes to have a personalized .htaccess for Apache,
and so more, so I won't ask them what -except paying enough for

.htaccess has nothing to do with whether you use .so or .a libraries.

Generally though, I doubt that there is a sufficient demand for static
linked versions of Lynx, for anyone to have one available for download
for your platform.

David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.

-- :
Micro$oft has a majority market share in the new desktop PC marketplace.
This is a bug, which Ubuntu is designed to fix !

Lynx-dev mailing list

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]