gawk-5.4.1 without linking to mpfr fails to build gcc 16.2.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- shell
- Domain
- build-system, tooling
Research direction
Start with the upstream gawk report and the linked workaround commit, then inspect the gawk package recipe in void-packages to see how it is built and whether it links to mpfr. Reproduce by compiling the newest GCC as described; done when the package builds with the required mpfr support and GCC compiles without the reported option errors.
Written by the indexing model from the issue text.
Description
Is this a new report?
Yes
System Info
Void 6.18.56_1 x86_64 GenuineIntel uptodate r
Package(s) Affected
gcc-16.2.0
Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://lists.gnu.org/archive/html/bug-gawk/2026-07/msg00020.html
Expected behaviour
While trying to build gcc 16.2.0 I get many errors like:
27216 #error 0Wabsolute-value does not have a Var() flag
options.cc:27292:2: error: #error 0Wexpansion-to-defined does not have a Var() flag
and similar. See the link to upstream list.
gawk should be linked to mpfr to be usable. Workaround:
https://cgit.git.savannah.gnu.org/cgit/gawk.git/commit/?id=bf85f8a3175af703597082d4c7e0abc2066a44d3
Actual behaviour
gawk should be able to build new gcc.
Steps to reproduce
Compile newest gcc.
- Dominant language
- Shell
- Stars
- 3.5k
- Forks
- 2.8k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 325
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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 void-linux/void-packages
-
bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
void-linux/void-packages#63249 · 3 comments ·
Maintainers usually reply within 1 day
-
xmlto: sources no longer available from upstreamPossibly taken @L1TerminalFault claimed this 4 days ago. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63237 ·
Maintainers usually reply within 1 day
-
AI 🤖 bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
void-linux/void-packages#63041 · 1 comment ·
Maintainers usually reply within 1 day
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63016 ·
Maintainers usually reply within 1 day
-
nextcloud-client: VFS plugins installed where the client does not searchMay be free again A pull request for this issue was closed without being merged. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
void-linux/void-packages#62700 ·
Maintainers usually reply within 1 day
All issues in void-linux/void-packages
Similar issues
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
ysb3996-blip/oops#51 ·
Maintainers usually reply within 1 day
-
luaebpf: the by-example page's intro names two outcomes of a lowering and omits the stop with the default verdictPossibly taken A pull request linked to this issue is open or already merged. Opendocumentation severity: low
Difficulty 1/5 Under an hour Newbie friendliness 88/100
luainkernel/lunatik#2231 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dataiku/kiji-proxy#668 ·
Maintainers usually reply within 2 days
-
diagnostics good first issue testing
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Remove leftover Cloud66 custom_web process from ProcfilePossibly taken @ShahadatTest claimed this today. OpenDifficulty: Easy Good First Issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
rubyforgood/casa#7330 · 1 comment ·
Maintainers usually reply within 1 day