Snap building fails due to missing include directory
Metadata
Current evaluation
Closed without documented fix. Snapcraft 2.4 failed builds by statically referencing non-existent include directories, requiring manual creation to bypass.
Suggested action: —
No scores available.
Issue body
Building the current network-manager snap (from https://code.launchpad.net/~morphis/+junk/nm-snap) on xenial with snapcraft 2.4 fails due to the following build errors
cc1: error: /home/simon/Work/ubuntu/snappy/nm-snap/stage/include: No such file or directory [-Werror=missing-include-dirs]
cc1: error: /home/simon/Work/ubuntu/snappy/nm-snap/stage/include/x86_64-linux-gnu: No such file or directory [-Werror=missing-include-dirs]
Both directories are not present and creating them satisfies the build. Looks like snapcraft is defining those two directories statically but doesn't make sure they exist.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without documented fix. Snapcraft 2.4 failed builds by statically referencing non-existent include directories, requiring manual creation to bypass. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as abandoned. Snapcraft 2.4 failed builds by referencing non-existent include directories. Manually creating the paths resolved the issue locally. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1772584 Having a "snap" directory with actual content causes build failures | snapcraft (launchpad) | closed | Closed without resolution or linked pull request. The proposed fix to allow alternative snap directories and update ignore rules was never implemented, indicating the issue was abandoned due to inactivity. |