| Summary: | Configure fails on Solaris 9 | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | David Highley <dhighley> |
| Component: | Build system | Assignee: | OpenSSH Bugzilla mailing list <openssh-bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | -current | ||
| Hardware: | SPARC | ||
| OS: | Solaris | ||
|
Description
David Highley
2003-05-26 16:18:57 AEST
That sounds like a compiler or openssl installation problem. Can you recompile openssl? I have just successfully configured openssh on Solaris 8 with gcc-3.3 here, which gave me: Linker flags: -L/usr/local/ssl/lib -R/usr/local/ssl/lib -L/usr/local/lib -R/usr/local/lib Libraries: -lrt -lz -lsocket -lnsl -lcrypto Well this almost works: gcc -o junk2 -I/usr/local/ssl/include -L/usr/local/ssl/lib -L/usr/local/lib -R/usr/local/lib junk2.c -lrt -lz -lsocket -lnsl -lcrypto It still fails with an unresolved reference to libgcc_s.so.1. This is a new platform being build from the ground up so I suspect a tool issue here. Note the suttle parameter order change of moving the source file a head of the library flags. I hope this does not indicate a reverting to where building software was a fragile task of determining what order you needed to things on the command line. Bottom line, not a bug. Still need to figure out why the C library is not being found when the code is linked with a -R flag. This is why shared libraries are really a failed academic concept. Mass change of RESOLVED bugs to CLOSED |