---
- branch: MAIN
  date: Fri Feb 11 21:44:11 UTC 2022
  files:
  - new: '1.1012'
    old: '1.1011'
    path: src/usr.bin/make/var.c
    pathrev: src/usr.bin/make/var.c@1.1012
    type: modified
  id: 20220211T214411Z.cc7b755d54389a7e026063801af3e8796f182cae
  log: |
    make: remove comment about environment variable with empty name

    At least on NetBSD, make cannot be fooled with an environment variable
    having an empty name.  When running '/usr/bin/env =undefined make', the
    argument is parsed as a variable assignment, but putenv(3) refuses to
    process an empty variable name.  Calling execve(2) directly got a step
    further, the kernel didn't filter '=undefined' from the environment
    variables.  But getenv(3) always returns NULL when querying the
    environment variable with the empty name.

    On other operating systems, things may be different.  Trying to set an
    environment variable with an empty name may cause errors in env(1),
    putenv(3), execve(2), getenv(3) or other places, so don't add an
    automatic test for now.
  module: src
  subject: 'CVS commit: src/usr.bin/make'
  unixtime: '1644615851'
  user: rillig