| Anonymous | Login | Signup for a new account | 06-08-2026 21:00 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0003217 | [Resin] | minor | always | 01-05-09 09:32 | 08-24-09 19:42 | ||||
| Reporter | ferg | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | urgent | Resolution | no change required | ||||||
| Status | closed | Product Version | |||||||
| Summary | 0003217: Solaris build -lcrypto in /usr/local/lib | ||||||||
| Description |
(rep by Eric Bowman) The 3.1.x variants work OK on Solaris, but I can only run Resin on my build system, not my deploy system. This is because on the build system, the Resin build finds -lcrypto in /usr/lib/security. On the production system, -lcrypto is in /usr/local/lib so Resin won't start. It's easy enough to tell configure to find all the other libraries it needs, what can I do about -lcrypto? |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |