← Back to issue list

Snap building fails due to missing include directory

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1558965
Type
issue
State
closed
Author
~morphis
Labels
—
Created
Updated
Closed

Current evaluation

Fixed by merged PR snapcraft#397: configured include and library paths are now ensured to exist before use.

Resolution: closed resolved

Reason: PR snapcraft#397, titled “Include and library paths must exist,” merged commit b7e19865f and resolved the missing stage/include directory errors.

Evaluated by: mr-cal-bot

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
stealth/space-bunny-alpha — closed resolved Fixed by merged PR snapcraft#397: configured include and library paths are now ensured to exist before use.
stealth/space-bunny-alpha — closed resolved Fixed in commit b7e19865f by creating referenced include and library directories, preventing Snapcraft 2.4 stage/include build failures.
stealth/space-bunny-alpha — closed resolved Fixed in commit b7e19865f by ensuring referenced include and library directories exist, resolving the Snapcraft 2.4 stage/include build failure.
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

Date Change
created

Related work

  • Likely Fixed By: snapcraft#397 (confidence 99%)

    Merged PR explicitly addressing the reported path-existence failure.

  • Likely Fixed By: snapcraft@b7e19865f (confidence 98%)

    Resolving commit included with the merge of PR #397.

Related issues

Issue Project State Summary Similarity
#1548232 Snapcraft messes with include path precedence in unhealthy ways snapcraft (launchpad) closed Include-path precedence was corrected by pkg-config work in canonical/snapcraft#429 (commit a117bd273), with a regression test added.
75%
#1661391 snap directory excluded from cleanbuild tarball snapcraft (launchpad) closed Cleanbuild now includes snap/ in its source tarball, fixing missing snap/snapcraft.yaml; merged via snapcore/snapcraft#1102 (e35826ed4).
71%
#1772584 Having a "snap" directory with actual content causes build failures snapcraft (launchpad) closed Resolved by adding build-aux as an alternative location for Snapcraft assets, preserving source-tree snap directories; merged in snapcraft#2496 and #2551.
70%