enroot hangs up fuse_overlayfs by trying a circular mount dependency
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux, shell
- Domain
- build-system
Research direction
Start with the repository Makefile and the make install path described in the report, then inspect the FORCE_GLIBC branch and the reported fuse_overlayfs hang on Rocky Linux 8.6. Reproduce the failure if possible and compare the documented package requirements with the EL8 build process; done means the build instructions or implementation address the reported failure.
Written by the indexing model from the issue text.
Description
To make it simple: Despite following the instructions what packages are required etc the 'elaborate' ;) build instructions of 'make install' do not work on my EL8 system (up to date Rocky Linux 8.6).
As there are no EL8 rpms in the release process I am forced to build it myself, but to no avail.
I get this message:
I tried to understand what Makefile is trying to do there, but I do not get it. Isn't it supposed to use the musl distribution it clones?
Is there any more elaborate build documentation?
I am stuck...although I have actually quite a bit of experience custom-compiling software. But this does not follow any standard configure or cmake-style buildflow and I wasn't able to find any further docs on the Makefile system sued in this project.
Any advice?
P.S.: In an effort to 'reverse-engineer' the Makefile I tried setting the FORCE_GLIBC env variable, this runs some build process, but ultimately gets stuck here:
This system has been used to build all kind of software for the cluster, so the gcc, g++ etc. build tool are all there and most definitely work.
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/enroot
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·