libkkc FTBFS on noble: can't resolve libraries to shared libraries: m

Bug #2065902 reported by Shengjing Zhu
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gobject-introspection (Debian)
Fix Released
Unknown
gobject-introspection (Ubuntu)
Fix Released
Undecided
Unassigned
Noble
Triaged
Undecided
Unassigned
libkkc (Debian)
Confirmed
Unknown
libkkc (Ubuntu)
Fix Released
Undecided
Unassigned
Noble
Triaged
Undecided
Unassigned

Bug Description

[ Impact ]

 * libkkc-dev is missing from armhf/noble, and is FTBFS everywhere on noble, due the regression in gobject-introspection.

[ Test Plan ]

 * gobject-introspection is built and published on noble.
 * do no-change rebuild for libkkc, and libkkc is built successfully on noble.

[ Where problems could occur ]

 * after the gobject-introspection upload, libkkc still FTBFS, but we will test it in PPA first.

[ Other Info ]

* no

[Original description]

https://launchpadlibrarian.net/730249695/buildlog_ubuntu-noble-amd64.libkkc_0.3.5-8_BUILDING.txt.gz

libtool: link: ( cd ".libs" && rm -f "libmarisa-glib.la" && ln -s "../libmarisa-glib.la" "libmarisa-glib.la" )
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=3" CFLAGS="-g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/libkkc-0.3.5-8 -Wall -pedantic" LDFLAGS="-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,--as-needed" CC="gcc" PKG_CONFIG="/usr/bin/pkg-config" GI_HOST_OS="" DLLTOOL="false" /usr/bin/x86_64-linux-gnu-g-ir-scanner --add-include-path=. --namespace=Marisa.gir --nsversion=Marisa --libtool="/bin/bash ../libtool" --include=GLib-2.0 --include=GObject-2.0 --include=Gio-2.0 --library=libmarisa-glib.la --pkg-export=marisa-glib --pkg=marisa --namespace=Marisa -lstdc++ -lm -lgcc_s -lc -lgcc_s --cflags-begin -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount -I/usr/include/blkid -I.. --cflags-end marisa-key.cc marisa-keyset.cc marisa-agent.cc marisa-trie.cc marisa-key.h marisa-keyset.h marisa-agent.h marisa-trie.h libmarisa-glib.la --output Marisa.gir
g-ir-scanner: link: /bin/bash ../libtool --mode=link --tag=CC gcc -o /<<PKGBUILDDIR>>/marisa-glib/tmp-introspectr0zhwjn5/Marisa-Marisa -export-dynamic -Wdate-time -D_FORTIFY_SOURCE=3 -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/libkkc-0.3.5-8 -Wall -pedantic /<<PKGBUILDDIR>>/marisa-glib/tmp-introspectr0zhwjn5/Marisa-Marisa.o -L. libmarisa-glib.la -lstdc++ -lm -lgcc_s -lc -lgcc_s -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lglib-2.0 -lmarisa -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,--as-needed
libtool: link: gcc -o /<<PKGBUILDDIR>>/marisa-glib/tmp-introspectr0zhwjn5/Marisa-Marisa -Wdate-time -D_FORTIFY_SOURCE=3 -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/libkkc-0.3.5-8 -Wall -pedantic /<<PKGBUILDDIR>>/marisa-glib/tmp-introspectr0zhwjn5/Marisa-Marisa.o -Wl,--export-dynamic -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z -Wl,relro -Wl,--as-needed -Wl,--export-dynamic -L. ./.libs/libmarisa-glib.a -lstdc++ -lm -lc -lgcc_s -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lmarisa -pthread
ERROR: can't resolve libraries to shared libraries: m

Related branches

Revision history for this message
Shengjing Zhu (zhsj) wrote :

The FTBFS results libkkc/0.3.5-8build1(https://launchpad.net/ubuntu/+source/libkkc/0.3.5-8build1) removed from noble before release. And the armhf binary libkkc-dev/0.3.5-8 is also removed from noble (not sure why, the log says ANAIS but not true) https://launchpad.net/ubuntu/noble/armhf/libkkc-dev/.

This results https://launchpad.net/ubuntu/+source/fcitx-kkc/0.1.4-3build5/+build/28050958 and https://launchpad.net/ubuntu/+source/fcitx5-kkc/5.1.1-1build3/+build/28002556 can't be built on noble armhf.

Revision history for this message
Shengjing Zhu (zhsj) wrote (last edit ):

The root cause is from gobject-introspection https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060951

Changed in gobject-introspection (Ubuntu Oracular):
status: New → Fix Released
Revision history for this message
Shengjing Zhu (zhsj) wrote :

The only difference between gobject-introspection oracular/1.80.1-3 and noble/1.80.1-1 is the fix for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060951. So a backport of gobject-introspection/1.80.1-3 to noble is sufficient.

Revision history for this message
Shengjing Zhu (zhsj) wrote :

after backport gobject-introspection, we need a NRC for libkkc in noble to bring back the armhf binary.

Changed in libkkc (Ubuntu Oracular):
status: New → Fix Released
Revision history for this message
Shengjing Zhu (zhsj) wrote (last edit ):

And ibus-anthy is also removed from noble because of this bug in gobject-introspection, maybe we should bring it back as well.

Shengjing Zhu (zhsj)
description: updated
Changed in gobject-introspection (Debian):
status: Unknown → Fix Released
Jeremy Bícha (jbicha)
no longer affects: libkkc (Ubuntu Oracular)
no longer affects: gobject-introspection (Ubuntu)
no longer affects: gobject-introspection (Ubuntu Oracular)
no longer affects: gobject-introspection (Ubuntu Noble)
no longer affects: libkkc (Ubuntu Noble)
Changed in gobject-introspection (Ubuntu):
status: New → Fix Committed
status: Fix Committed → Fix Released
Changed in gobject-introspection (Ubuntu Noble):
status: New → Triaged
Changed in libkkc (Ubuntu Noble):
status: New → Triaged
Changed in libkkc (Debian):
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.