Page MenuHomeFreeBSD

makesyscalls.sh: always use absolute path for syscalls.conf
ClosedPublic

Authored by brooks on May 30 2019, 8:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 14 2024, 7:29 PM
Unknown Object (File)
Jan 13 2024, 11:28 AM
Unknown Object (File)
Dec 20 2023, 8:40 AM
Unknown Object (File)
Sep 10 2023, 12:43 PM
Unknown Object (File)
Sep 5 2023, 11:23 PM
Unknown Object (File)
Sep 5 2023, 11:21 PM
Unknown Object (File)
Sep 5 2023, 11:20 PM
Unknown Object (File)
Sep 5 2023, 11:20 PM
Subscribers

Details

Summary

syscalls.conf is included using "." which per the Open Group:

If file does not contain a <slash>, the shell shall use the search path
specified by PATH to find the directory containing file.

POSIX shells don't fall back to the current working directory.

Submitted by: Nathaniel Wesley Filardo <nwf20@cl.cam.ac.uk>

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 24609
Build 23392: arc lint + arc unit

Event Timeline

bdrewery added inline comments.
sys/compat/cloudabi64/Makefile
15

Please use ${.CURDIR} instead of ./ in all of this. That will churn less with my change which does that.

This revision now requires changes to proceed.May 30 2019, 8:43 PM
  • Use ${.CURDIR} instead of ".".
This revision is now accepted and ready to land.May 30 2019, 8:50 PM
brooks retitled this revision from makesyscalls.sh: always use relative path for syscalls.conf to makesyscalls.sh: always use absolute path for syscalls.conf.May 30 2019, 8:54 PM
This revision was automatically updated to reflect the committed changes.