News Group Posts

ssh binaries binary packages libz.so.1

Date: Sat, 16 Mar 2002 12:00:40 -0500
From: Tony Lawrence <tony@aplawrence.com>
Subject: Re: How on earth, was Re: New OpenSSH packages available (3.1p1)

Jean-Pierre Radley wrote:

> Tony Lawrence propounded (on Sat, Mar 16, 2002 at 01:12:50PM +0000):
> | How an earth is an ordinary human being ever supposed to get ssh working 
> | on OSR5?
> | 
> | I'm not the most technical geek the workd has ever seen, but I have at 
> | least a few skills, and I find this horribly frustrating.
> | 
> | I installed a new 5.0.6 system and tried the Caldera Openssh link. 
> | Great fun finding that: would it kill to DESCRIBE what these packages are?
> | 
> | Immediate failure of course because it needs /usr/local/lib/libz.so.1
>

Stuff deleted


> | I'm frustrated and angry- how is someone with less skills, knowledge and 
> | resources going to feel?
> 
> Let me know if my tarball works.  Prng isn't involved, and while libz is
> certainly used, I built ssh with a static zlib.a instead of a dynamic
> one.   It's opensshOSR5.tar.bz2 at ftp.jpr.com.


BTW, the "disconnect" problem was just the "scoansi" TERM problem- the 
system I was sshing to doesn't like that.  I remembered that on my way 
to the gym.  A simple "export TERM=ansi" fixed it.

To know if your tarball truly is self standing, I have to back out 
everything I've done first. But the point isn't that you CAN build and 
package programs to be independent of other packages, the point is that 
SCO/Caldera Skunkware doesn't even try.  Yes, I understand Skunkware is 
a volunteeer effort, but I'm sure the intentions of the volunteers is 
NOT to further frustrate people who came there looking to add 
functionality to their system.  None of us who provide freebies WANT to 
frustrate anyone, and we can never completely avoid it, but we should at 
least try- you don't want your efforts to end up having a negative 
outcome because that doesn't help anyone.

The problem, of course, is that the typical developer already has all 
kinds of stuff already installed on their system, and just doesn't take 
the time to compare a ldd with what is "stock".  Of course, even if they 
did so, I know of no easy method on OSR5 to trace back where a 
particular library could have come from.

I'd like to suggest that this is a FAQ and Skunkware project that some 
of us here could contribute to: a cross reference of libraries to 
packages that need them and the packages that will provide them.  It 
shouldn't be all that hard to do- it's just a lot of ldd'ing and 
examination of Skunkware VOL's.

To that end, I added c.u.s.p  and I hope that we can get a few 
volunteers because it will take me forever to get it done.  I would 
imagine that Skunkware would happily publish this, and of course I will 
too and will index it by library so folks can nail what they need quickly.

Thoughts?



 


-- 
Tony Lawrence
SCO/Linux Support Tips, How-To's, Tests and more: 

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.