Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #19028

Closed (moved)
(moved)
Open
Created May 11, 2016 by cypherpunks@cypherpunks

Merge the header checks in configure.ac

The build configuration contains two sets of header checks where one checks headers that are deemed essential and one checks headers that are not. The only difference being that missing essential headers display a non-fatal warning when they aren't found.

For the following reasons i think it is better to merge the sets and discard the warning.

  • Commit e8cc839e41adc4975a61fee62abe7f6664fd0c0e adds sys/capability.h to the essential header set but Tor runs fine without capabilities being available. IMO it is in the wrong set.
  • Having two sets requires developers to make a choice whether headers are essential or not. Instead developers should write code that handles cases where the headers are unavailable (like the capabilities code).
  • The current warning is truncated because its message is incorrectly quoted. This means the part about sending the orconfig.h file isn't shown and has been ineffective.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking