[Bug libelf/32293] New: Build of vl4-utils using elfutils-0.192 libelf (static) fails
https://sourceware.org/bugzilla/show_bug.cgi?id=32293 Bug ID: 32293 Summary: Build of vl4-utils using elfutils-0.192 libelf (static) fails Product: elfutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: libelf Assignee: unassigned at sourceware dot org Reporter: rudi at heitbaum dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- The new eu functions are included in libelf but linkage against libelf fails as below. Believe that this is occurring since https://sourceware.org/git/?p=elfutils.git;a=commit;h=d6443d1a4df6057f9012d105037f52daaca911f1 libeu.a is not installed, so whilst libeu.a has been built, unsure what is suppose to be the correct linkage when statically linking? /build/build.LibreELEC-Generic.x86_64-13.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/libelf.a(elf_begin.o):elf_begin.c:function file_read_elf:(.text+0x38b): error: undefined reference to 'eu_search_tree_init' /build/build.LibreELEC-Generic.x86_64-13.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/libelf.a(elf_begin.o):elf_begin.c:function file_read_elf:(.text+0x4cb): error: undefined reference to 'eu_search_tree_init' /build/build.LibreELEC-Generic.x86_64-13.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/libelf.a(elf_end.o):elf_end.c:function elf_end:(.text+0xb0): error: undefined reference to 'eu_search_tree_fini' -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32294] New: configure fails without rpm support
https://sourceware.org/bugzilla/show_bug.cgi?id=32294 Bug ID: 32294 Summary: configure fails without rpm support Product: elfutils Version: unspecified Status: NEW Severity: normal Priority: P2 Component: debuginfod Assignee: unassigned at sourceware dot org Reporter: doko at debian dot org CC: elfutils-devel at sourceware dot org Target Milestone: --- seen with 0.192, CFLAGS="-g -O3 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection" CXXFLAGS="-g -O3 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" \ ./configure --build=x86_64-linux-gnu --enable-maintainer-mode --prefix=/usr \ --sysconfdir=/etc \ --libdir=/usr/lib/x86_64-linux-gnu \ --program-prefix=eu- --disable-silent-rules \ --enable-libdebuginfod --enable-debuginfod --enable-debuginfod-urls="https://debuginfod.debian.net"; [...] checking for zstd... yes checking whether g++ supports C++11 features with -std=c++11... yes checking for execinfo.h... yes checking for pkg-config... (cached) /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for libcurl >= 7.29.0... yes checking for pthread_setname_np in -lpthread... yes checking for json-c >= 0.11... no checking for libmicrohttpd >= 0.9.33... yes checking for libmicrohttpd < 0.9.51... no checking for sqlite3 >= 3.7.17... yes checking for libarchive >= 3.1.2... yes checking for headerGet in -lrpm... no checking for EVP_MD_CTX_new in -lcrypto... yes checking for imaevm.h... yes configure: error: unable to build libdebuginfod make: *** [debian/rules:70: stamps/configure] Error 1 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug debuginfod/32294] configure fails without json-c support
https://sourceware.org/bugzilla/show_bug.cgi?id=32294 Mark Wielaard changed: What|Removed |Added Summary|configure fails without rpm |configure fails without |support |json-c support CC||mark at klomp dot org --- Comment #1 from Mark Wielaard --- The error message is confusing. The issue isn't missing rpm headerGet support (that will disable Debuginfod RPM sig checking). But the missing json-c support (which is now mandatory to build libdebuginfod). We should improve the configure error message here. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug libelf/32293] Build of vl4-utils using elfutils-0.192 libelf (static) fails
https://sourceware.org/bugzilla/show_bug.cgi?id=32293 Mark Wielaard changed: What|Removed |Added CC||mark at klomp dot org --- Comment #1 from Mark Wielaard --- Is there a reason vl4-utils cannot simply be linked shared to libelf? In general we aren't really testing static linking. Which indeed means it is now broken :{ Maybe something like the following would help? diff --git a/libelf/Makefile.am b/libelf/Makefile.am index 3402863ef174..2d3dbdf22756 100644 --- a/libelf/Makefile.am +++ b/libelf/Makefile.am @@ -122,6 +122,9 @@ libelf.so: $(srcdir)/libelf.map $(libelf_so_LIBS) $(libelf_so_DEPS) @$(textrel_check) $(AM_V_at)ln -fs $@ $@.$(VERSION) +libeu_objects = $(shell $(AR) t ../lib/libeu.a) +libelf_a_LIBADD = $(addprefix ../lib/,$(libeu_objects)) + install: install-am libelf.so $(mkinstalldirs) $(DESTDIR)$(libdir) $(INSTALL_PROGRAM) libelf.so $(DESTDIR)$(libdir)/libelf-$(PACKAGE_VERSION).so I don't have anything to test that with though. (You'll need to autoregen -f -v -i) -- You are receiving this mail because: You are on the CC list for the bug.