|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3217 | minor | always | 01-05-09 09:32 | 08-24-09 19:42 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | no change required | |||
| Projection: | none | ||||
| ETA: | none | Fixed in 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? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||
|
|
|||||
|
|
||||