-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Restore build on old systems without openat(2) (re: 3d7b7e1)
The openat system call was standardised by POSIX in 2008, which is still too recent for it to be portable on systems older than a decade or so. I have two old systems that it breaks on. src/lib/libast/features/lib: - Add simple lib test for openat(2), defining _lib_openat if found. This will be available wherever <ast.h> is included. src/cmd/ksh93/*/*.[ch]: - Restore the tried-and-tested cd_pwd.c and subshell.c code from before the referenced commit as a fallback for systems that don't have openat(2), i.e.: it is used #if !_lib_openat. - However, the even older pre-fchdir(2) code is not restored. Additionally, a couple of build system workarounds for old systems: src/cmd/INIT/mamake.c: - Do not set fictional future _POSIX_SOURCE and _X_OPEN_SOURCE version macros. The system headers on (at least) QNX 6.5.0 and Solaris 10.1 don't like them. (re: f58153d) src/cmd/INIT/include/link_ar.mam: - Compensate for the lack of 'ar -s' by falling back to pre-POSIX 'ranlib'. Solaris 10.1 needs this. (re: 2ad0f54) Resolves: ksh93#816
- Loading branch information
Showing
9 changed files
with
94 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters