[Build Error] Failed to compile GCC 11.4.0 in SRS-ue-base: bits/largefile-config.h No such file or directory
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, shell
- Domain
- build-system, devops
Research direction
Start with README.md and jrtc-apps/containers/Docker/build_srs_ue_base.sh, then inspect the Dockerfile dependency installation and the GCC 11.4.0 build logs around libstdc++-v3/configure. Reproduce with ./build_srs_ue_base.sh -c and compare the available headers and utilities in the CBL-Mariner base image. Done means the image builds successfully and the recommended command for SRS-UE testing is documented.
Written by the indexing model from the issue text.
Description
Description
I am experiencing a build failure while following the README.md instructions in the jrtc-apps/containers/ directory to build the SRS UE base image. The build process fails during the GCC 11.4.0 compilation stage (make -j$(nproc)).
Environment:
- Base Image: ghcr.io/microsoft/jrtc-apps/base/srs:latest (CBL-Mariner based)
- Target: Downgrading GCC from 13 to 11.4.0 inside the container.
- Command Executed: ./build_srs_ue_base.sh -c
Steps to Reproduce:
- Navigate to jrtc-apps/containers/Docker/.
- Run ./build_srs_ue_base.sh -c.
- Observe the build logs during the GCC compilation phase.
- Observed Error: The build fails during the make process of GCC 11.4.0 with the following error:
- Plaintext
/tmp/gcc-11.4.0/libstdc++-v3/configure: line 7784: /usr/bin/file: No such file or directory
...
make[3]: [Makefile:1767: x86_64-pc-linux-gnu/bits/largefile-config.h] Error 1 (ignored) - Additional Context:
Even after manually adding glibc-devel and file to the tdnf install list in the Dockerfile, the error persists.
It appears that the configure script fails to correctly identify the system architecture or header paths due to the missing file utility or mismatched header locations in the base image.
Questions:
- Is there a specific set of dependencies or a pre-configured base image required to avoid these header mismatch issues during GCC compilation?
- Once the Docker build is successfully completed, what is the recommended command/procedure to run the container for SRS-UE testing?
- Dominant language
- Python
- Stars
- 14
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 microsoft/jrtc-apps
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in microsoft/jrtc-apps
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100