Re: Path Problems with 4.2p1?
- From: Mark Olbert <ChairmanMAO@xxxxxxxxxxxxxxxxx>
- Date: Sun, 08 Jan 2006 15:03:49 -0800
I used ./configure --prefix=/usr to load the binaries into /usr/sbin rather than /usr/local/sbin (I've done the same things in
earlier versions of openssh and it's worked the way I expected it to).
I didn't try a make distclean before doing the initial configure and make. I tend to assume that building within a freshly-extracted
source tree is adequate...but I know that's not always true. I'll try that suggestion and see what happens.
Right now I've reverted to 4.1p. It builds fine, puts everything where I expect it to go, and doesn't gack on finding those files at
startup that were causing me the problem with 4.2p.
- Mark
.
- Follow-Ups:
- Re: Path Problems with 4.2p1?
- From: Darren Tucker
- Re: Path Problems with 4.2p1?
- References:
- Re: Path Problems with 4.2p1?
- From: Darren Tucker
- Re: Path Problems with 4.2p1?
- Prev by Date: Re: Passphraseless login using keychain
- Next by Date: PuTTY suddenly stopped working (WinXPsp2 to FreeBSD5.4)
- Previous by thread: Re: Path Problems with 4.2p1?
- Next by thread: Re: Path Problems with 4.2p1?
- Index(es):
Relevant Pages
|