| Summary: | Problem compiling openssh 4.7p1 | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Pierre <pierre42d> |
| Component: | Build system | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED INVALID | ||
| Severity: | normal | CC: | dtucker |
| Priority: | P2 | ||
| Version: | 4.7p1 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
|
Description
Pierre
2007-11-12 11:50:56 AEDT
What distro are you using, and what arguments did you give to openssh's configure? You have several libraries that I would not expect to see (eg gpm, searching the berkeley DB dirs).
> /bin/ld:
> warning: libcrypto.so.0.9.6, needed by /usr/local/lib/libopensc.so, not
> found (try using -rpath or -rpath-link)
This seems to indicate that your opensc library was built against a version of openssl that is no longer installed.
It's a LFS GNU/Linux system I used ./configure --with-zlib --with-skey --with-ssl-engine --with-pam --with-rand-helper --with-sectok --with-opensc --with-kerberos5 --with-md5-passwords I saw the error with opensc, but is it really the cause of the problem ? (In reply to comment #2) > It's a LFS GNU/Linux system > I used ./configure --with-zlib --with-skey --with-ssl-engine --with-pam > --with-rand-helper --with-sectok --with-opensc --with-kerberos5 > --with-md5-passwords > I saw the error with opensc, but is it really the cause of the problem Probably not, but it certainly casts serious doubt over the integrity of the system. I suspect you have one or more problems with your libraries being linked against other libraries that are now missing or replaced. Since every LFS system is effectively a custom one-of-a-kind, sorting it out is up to you. I suggest that you start by building openssh without any options. If that works, start adding options one at a time until it stops working, then remove *all* of the files associated with that package that breaks it (make sure you get ones in /usr/local as well as /usr/{lib,include}), rebuild the package then try openssh again. Repeat until everything you want works. I succeed to make it compile when I just removed the --with-opensc and --with-kerberos5 options. There must be a problem with these libs on my system, and I will try to recompile them properly. But maybe is it possible to add a check to the configure script to detect this kind of problems before the compilation ? (In reply to comment #4) > I succeed to make it compile when I just removed the --with-opensc and > --with-kerberos5 options. > There must be a problem with these libs on my system, and I will try to > recompile them properly. > But maybe is it possible to add a check to the configure script to > detect this kind of problems before the compilation ? Configure does a number of sanity checks but there's an almost infinite number of ways that a system can be broken so it's impossible for configure to check for all of them. Closing bug. *** Bug 1389 has been marked as a duplicate of this bug. *** Close resolved bugs after release. |