Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up build system, add .gitignore. #11

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Clean up build system, add .gitignore. #11

wants to merge 3 commits into from

Conversation

ericonr
Copy link
Member

@ericonr ericonr commented Aug 27, 2020

Removed the chkshsgr and systype checks. This one is still a bit WIP. Technically, chkshsgr checks if the build system can adequately run the hasshsgr test, so just removing it isn't the the best policy.

How should we alter the build style? Should it be made to support only platforms that we do / reasonably modern platforms, eliminating the need for all the choose checks we are doing, or should it be made to still work with all the platforms it originally did?

chkshsgr: This program is used to verify if the compilation environment
is enough to run getgroups() and setgroups().
0x5c added a commit to 0x5c/runit that referenced this pull request Mar 27, 2023
prot.c provides two functions: prot_gid and prot_uid.

prot_gid is fully unused, and depends on {chk,try}shsgr, both of which must be
run at build-time and require that the user has additional groups. They are not
needed by anything else and their removal gets rid of cross-compilation jank.

prot_uid is used (once) by chpst, but since it is a no-op wrapper around
setuid(), its use can be replaced by a normal call to setuid().

Solves the big questions from void-linux#11
0x5c added a commit to 0x5c/runit that referenced this pull request Mar 27, 2023
The "systype" machanism is merely a system info gatherer, and the info it
collects is (mostly) not used anywhere. The only seemingly important info is
the kernel and kernel version (or the lack thereof), and has been moved to
where it is used (print-ar.sh)

This gets rid of two cross-incompatible buildtime programs.
One tried to find if the build was happening on NeXT, but that's not an
operating system that print-ar.sh cares about. The other tried to do cpuid on
x86, which is useless to the build.

This seems to implement what void-linux#11 started.
@0x5c 0x5c mentioned this pull request Apr 4, 2023
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant