mapbox / mapbox/variant

error: size of array ‘altStackMem’ is not an integral constant-expression

Open
#183 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
384
Forks
96
PR merge metrics
No merged PRs in 30d

Description

As reported in [Debian Bug #1017327](https://bugs.debian.org/1017327):
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> ```
> Relevant part (hopefully):
> g++ -c -o out/issue122.o test/t/issue122.cpp -Iinclude -isystem test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2 -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread
> In file included from /usr/include/signal.h:328,
> from test/include/catch.hpp:6392,
> from test/unit.cpp:2:
> test/include/catch.hpp:6415:33: error: size of array ‘altStackMem’ is not an integral constant-expression
> 6415 | static char altStackMem[SIGSTKSZ];
> | ^~~~~~~~
> test/include/catch.hpp:6466:45: error: size of array ‘altStackMem’ is not an integral constant-expression
> 6466 | char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};
> | ^~~~~~~~
> mkdir -p ./out
> g++ -c -o out/mutating_visitor.o test/t/mutating_visitor.cpp -Iinclude -isystem test/include -std=c++11 -Werror -Wall -Wextra -pedantic -Wformat=2 -Wsign-conversion -Wshadow -Wunused-parameter -O3 -DNDEBUG -march=native -DSINGLE_THREADED -fvisibility-inlines-hidden -fvisibility=hidden -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread
> make[1]: *** [Makefile:96: out/unit.o] Error 1
> ```
>
> The full build log is available from:
> http://qa-logs.debian.net/2022/08/13/mapbox-variant_1.2.0-1_unstable.log

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing test/include/catch.hpp around lines 6392–6466 and reproducing the Debian build command for test/t/issue122.cpp or test/unit.cpp. Compare the failure with the linked Debian build log; done means the affected test sources compile successfully under the reported C++11 build flags.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.