Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 532
    • Issues 532
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #2358

Closed
Open
Created Dec 22, 2020 by Mark Andrews@markaOwner

Update CI to have poisoned header files

Update the CI to have a system with poisoned header files installed to detect when include order has been broken. The header files in the build / source tree should be found before these poisoned header files.

The contents of the poisoned header files should be something like #error fix include order.

/usr/include and /usr/local/include would be ideal locations to add poisoned header files.

#2357 (closed) is what happens when we don't detect this at development time. I used poisoned <isc/types.h> and <dns/types.h> when testing the fixes for #2357 (closed) but really should have every header file with poisoned versions.

Edited Dec 22, 2020 by Mark Andrews
Assignee
Assign to
Time tracking