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)
Wed, Feb 19, 10:04 PM
Unknown Object (File)
Tue, Feb 18, 7:13 AM
Unknown Object (File)
Sat, Feb 15, 1:22 PM
Unknown Object (File)
Sat, Feb 8, 10:37 PM
Unknown Object (File)
Sun, Feb 2, 4:03 PM
Unknown Object (File)
Sun, Feb 2, 3:49 PM
Unknown Object (File)
Jan 15 2025, 2:28 PM
Unknown Object (File)
Jan 10 2025, 5:25 AM
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

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

bdrewery added inline comments.
sys/compat/cloudabi64/Makefile
15 ↗(On Diff #58091)

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.