Very Computer

by **John Estes** » Wed, 22 Dec 1999 04:00:00

I tried to compile the openssh port for 3.3-S, but was returned an error
stating it couldn't find crypto.1. Knowing this group, I guess the
correct question to ask is "where is the man page?"

I think I download the crypto files while CVSupping. Are there the files
I want? Why aren't they installed? I do have USA_RESIDENT="YES", if that
matters...

Thank you,
--
_/ _/_/_/ || John Estess

_/_/_/ _/_/_/ || champion of the proactive Golden Rule
"Do unto others as they would to you, but do it first."

by **John Estes** » Wed, 22 Dec 1999 04:00:00

> >I tried to compile the openssh port for 3.3-S, but was returned an
> >error stating it couldn't find crypto.1. Knowing this group, I guess
> >the correct question to ask is "where is the man page?"

> Nope. The correct answer is: where's the dependency?

> Openssh depends on openssl, which contains the 'crypto' lib.
> FreeBSD uses a 'crypt' library wrapper for various crypto stuff of its
> own.

> scsprong

new woes erupt: when "make"ing openssl, it won't compile and I receive a
message stating I have the wrong version of Perl in /usr/bin. I
installed 3.2 and have updated ever since. It appears Perl is updated
during CVSup. Am I wrong? I've installed many ports, but I never had
this error. What can I do?

--
_/ _/_/_/ || John Estess

_/_/_/ _/_/_/ || C- FAQ: http://www.eskimo.com/~scs/C-faq/top.html

by **John Estes** » Wed, 22 Dec 1999 04:00:00

Quote:> I have done about the same maintenance as you and on my system
> openssl v0.9.4 + openssh v1.2 compiled witout errors. The openssl
> port file states it requires PERL5, which is generic Perl 5; mine
> is still Perl v5.005_03.

When did you do this? I should mention that when going to ports-stable,
I end in -current by a link. I wonder if this is an error. Also, I have
Perl v5.005_3 also. I have no love for Perl, it came with the system and
I haven't definitely haven't messed with it (Python rules :-) ).

Quote:> In your situation my strategy would be to check the integrity of the
> base system (BTW yet another reason to keep the base separate from the
> locally installed additions)

Base has been and always will be separate from the system. I'm a
* who updates and recompiles stable once or twice a week,
usually after I had one too many to code...

and then build the port by hand, carefully

Quote:> reviewing the port patches. If that would fail, I would try to retrieve
> older ports

I was in stable. If it worked for you, it really should work for me. I'm
look at it again this weekend.

(I always try to ram home that newer is hardly ever better,

Quote:> especially if the newer is a beta version. Never ever be dependent on
> beta.). If that would fail as well, I would write the ports maintainer
> and/or send a problem report to the ports mailing list.

> I can't do all that remotely, therefore I can't help you further.

No you can't, but I really appreciate your assistance. Thank you.

_/ _/_/_/ || John Estess

_/_/_/ _/_/_/ || C- FAQ: http://www.veryComputer.com/~scs/C-faq/top.html

by **S.C.Spro** » Thu, 23 Dec 1999 04:00:00

>I tried to compile the openssh port for 3.3-S, but was returned an
>error stating it couldn't find crypto.1. Knowing this group, I guess
>the correct question to ask is "where is the man page?"

Nope. The correct answer is: where's the dependency?

Openssh depends on openssl, which contains the 'crypto' lib.
FreeBSD uses a 'crypt' library wrapper for various crypto stuff of its
own.

scsprong

by **S.C.Spro** » Thu, 23 Dec 1999 04:00:00

>>>I tried to compile the openssh port for 3.3-S, but was returned an
>>>error
>>Openssh depends on openssl
>new woes erupt: when "make"ing openssl, it won't compile and I receive
>a message stating I have the wrong version of Perl in /usr/bin.

I have done about the same maintenance as you and on my system
openssl v0.9.4 + openssh v1.2 compiled witout errors. The openssl
port file states it requires PERL5, which is generic Perl 5; mine
is still Perl v5.005_03.

In your situation my strategy would be to check the integrity of the
base system (BTW yet another reason to keep the base separate from the
locally installed additions) and then build the port by hand, carefully
reviewing the port patches. If that would fail, I would try to retrieve
older ports (I always try to ram home that newer is hardly ever better,
especially if the newer is a beta version. Never ever be dependent on
beta.). If that would fail as well, I would write the ports maintainer
and/or send a problem report to the ports mailing list.

I can't do all that remotely, therefore I can't help you further.

Success,
scsprong

by **S.C.Spro** » Thu, 23 Dec 1999 04:00:00

[ I wrote ]

Quote:>>I have done about the same maintenance as you and on my system
>>openssl v0.9.4 + openssh v1.2 compiled witout errors. The openssl
>>port file states it requires PERL5, which is generic Perl 5; mine
>>is still Perl v5.005_03.
>When did you do this?

I built openssh on December 14th. My ports are from December 13th, but
I did retrieve them by hand, not with CVSup. Perhaps you have the
4.0-current ports? In the past I have run into enormous amounts of
trouble by inadvertently mixing different port trees, which is why I
don't automatically update them anymore.

Quote:>I end in -current by a link. I wonder if this is an error.

I don't know enough about the source structure to answer this; it
could.

scsprong

by **Erik Trulsso** » Mon, 27 Dec 1999 04:00:00

> [ I wrote ]
>>>I have done about the same maintenance as you and on my system
>>>openssl v0.9.4 + openssh v1.2 compiled witout errors. The openssl
>>>port file states it requires PERL5, which is generic Perl 5; mine
>>>is still Perl v5.005_03.
>>When did you do this?
> I built openssh on December 14th. My ports are from December 13th, but
> I did retrieve them by hand, not with CVSup. Perhaps you have the
> 4.0-current ports? In the past I have run into enormous amounts of
> trouble by inadvertently mixing different port trees, which is why I
> don't automatically update them anymore.
>>I end in -current by a link. I wonder if this is an error.
> I don't know enough about the source structure to answer this; it
> could.

There is only one ports tree which is used for both -current and -stable.
And OpenSSH and openssl both work just fine for me (running 3.3-stable, soon
to be 3.4-stable)
They both built without any problems at all.
(Just go to /usr/ports/security/openssh and write 'make install' and
everything *should* build and install.)

--
<Insert your favourite quote here.>
Erik Trulsson