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
F142476372: D20476.id58094.diff
Tue, Jan 20, 6:16 AM
Unknown Object (File)
Mon, Jan 19, 4:49 AM
Unknown Object (File)
Mon, Jan 19, 3:43 AM
Unknown Object (File)
Sun, Jan 18, 8:04 PM
Unknown Object (File)
Sun, Jan 18, 1:34 PM
Unknown Object (File)
Thu, Jan 8, 9:15 PM
Unknown Object (File)
Sun, Jan 4, 10:36 AM
Unknown Object (File)
Fri, Dec 26, 11:28 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.