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)
Mon, Nov 3, 12:58 AM
Unknown Object (File)
Fri, Oct 31, 4:54 AM
Unknown Object (File)
Tue, Oct 28, 8:17 AM
Unknown Object (File)
Sat, Oct 25, 11:11 PM
Unknown Object (File)
Sun, Oct 19, 6:17 AM
Unknown Object (File)
Sat, Oct 18, 5:57 PM
Unknown Object (File)
Sat, Oct 18, 5:57 PM
Unknown Object (File)
Sat, Oct 18, 5:57 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 24610
Build 23393: 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.