Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #19174

Closed (moved)
(moved)
Open
Created May 25, 2016 by Nick Mathewson@nickm🏃

libscrypt check fails when libscrypt requires libm

See #19161 (moved) for background.

When libscrypt requires libm, our current check fails to detect libscrypt. This caused a failure to build (#19161 (moved)), which we fixed by not calling libscrypt_scrypt() unless that function was actually found.

But we still have a problem here: We would like to detect libscrypt in these cases, and actually use it as appropriate.

Isis and I wrote a solution in isis's branch bug19161_028, but it has some remaining infelicities, I think. Will transcribe those in a comment.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking