Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 577
    • Issues 577
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 116
    • Merge requests 116
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • 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 ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #785
Closed
Open
Issue created Dec 17, 2018 by Ghost User@ghost

configure wrongly warns about non-POSIX shell

Summary

configure always warns about the shell being non-POSIX, even when it is.

BIND version used

Bug in 9.13.4,5, not in 9.12.3

Steps to reproduce

Prepare the installation source by unpacking a source archive or otherwise.

In the top-level directory of the source, run ./configure [options] from eg dash as /bin/sh.

What is the current bug behavior?

A warning that configure will continue with the shell even though it is non-POSIX is interleaved in the command output.

What is the expected correct behavior?

configure should recognise /bin/sh (or possibly some other shell in its search path) as being POSIX enough and not display a warning.

Possible fixes

The sufficient condition is based on $(expr ...) and $((...)) being supported and giving the same result.

The script fragment ca. line 11680 in configure that assesses the available shells against this condition uses a loop that fails to exit. Consequently it always finds the guard value "no".

After line 11702, when the sufficiently POSIX shell has been found and stashed in a variable, append a line

break
Assignee
Assign to
Time tracking