← Back to issue list

snapcraft 2.27 fails to build the mosh classic snap

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1665089
Type
issue
State
closed
Author
~elopio
Labels
classic
Created
Updated
Closed

Current evaluation

Resolved by snapcraft#1146, restoring reverted libc symlinks needed for classic-confinement builds such as mosh. Merged as commit 0f4872241.

Resolution: closed resolved

Reason: snapcraft#1146 restored the reverted libc symlinks and was merged as commit 0f4872241, addressing the Snapcraft 2.27 classic-build regression.

Evaluated by: mr-cal-bot

No scores available.

Issue body

The mosh classic snap builds fine with snapcraft 2.26, but fails in 2.27 with: /usr/bin/ld: /home/ubuntu/workspace/mobile-shell/mosh/parts/mosh/install/usr/lib/x86_64-linux-gnu/libutil.a(forkpty.o): relocation R_X86_64_PC32 against undefined symbol `fork@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status Makefile:421: recipe for target 'mosh-server' failed make[3]: *** [mosh-server] Error 1 To reproduce: $ git clone https://github.com/elopio/mosh $ cd mosh $ git checkout snapcraft $ snapcraft

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Resolved by snapcraft#1146, restoring reverted libc symlinks needed for classic-confinement builds such as mosh. Merged as commit 0f4872241.
stealth/space-bunny-alpha — closed resolved Fixed the Snapcraft 2.27 classic-snap linker regression by restoring libc symlinks in PR #1146, commit 0f4872241.
stealth/space-bunny-alpha — closed stale Snapcraft 2.27's mosh classic-snap link failure was closed without a fix or explanation; the missing -fPIC/forkpty build problem was abandoned.
qwen/qwen3.6-35b-a3b — — Abandoned. The snapcraft 2.27 build failure for the mosh classic snap, caused by missing -fPIC linker flags, was closed without resolution or comments. Likely resolved in later snapcraft versions.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The snapcraft 2.27 linker failure for mosh classic snaps caused by missing -fPIC flags was abandoned due to inactivity, likely superseded by newer snapcraft releases.
qwen/qwen3.6-35b-a3b — — Closed without resolution or comments. The snapcraft 2.27 linker error was likely abandoned or resolved by the author, as no fix or discussion was recorded.
qwen3.6-35b-a3b-mtp-q6 — — Closed without resolution. The snapcraft 2.27 linker failure blocking mosh classic snap builds was not patched and superseded by newer releases.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcraft#1146 (confidence 96%)

    The PR restored libc symlinks removed by #1100, matching classic-confinement compatibility needs.

Related issues

Issue Project State Summary Similarity
#1650946 unhelpful error when building a classic snap: classic confinement requires the core_dynamic_linker to be set snapcraft (launchpad) closed Resolved: the cryptic "classic confinement requires the core_dynamic_linker to be set" error was fixed by snapcore/snapcraft PR #1025 (better diagnostic) and PR #1112 / commit 49b39ef9a, which auto-installs/unpacks the core snap; Launchpad builds snapcraft 2.27+ via LP: #1650946.
71%
#1647699 Support classic building in snapcraft snapcraft (launchpad) closed Classic-snap builds were implemented by merged snapcore/snapcraft#949 (commit 058f5626d), resolving libraries from the core/base snap.
71%
#1817300 autotools plugin fails to build in classic confinement snapcraft (launchpad) closed Fixed classic-confinement builds broken by core-snapcraft library paths after a Xenial libc6 update; #2485 landed as commit a8fce1ae5, alongside #2484.
70%
#949 project: support building classic snaps snapcraft merged Merged PR #949 in commit 058f5626d, adding classic-snap build support and core-snap path configuration.
70%