public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
* [Bug libelf/31034] New: iproute2 fails to build with elfutils 0.190 with musl libc
@ 2023-11-06 11:43 ncopa at alpinelinux dot org
  2023-11-06 11:50 ` [Bug libelf/31034] " ncopa at alpinelinux dot org
  2023-12-21  0:55 ` mark at klomp dot org
  0 siblings, 2 replies; 3+ messages in thread
From: ncopa at alpinelinux dot org @ 2023-11-06 11:43 UTC (permalink / raw)
  To: elfutils-devel

https://sourceware.org/bugzilla/show_bug.cgi?id=31034

            Bug ID: 31034
           Summary: iproute2 fails to build with elfutils 0.190 with musl
                    libc
           Product: elfutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libelf
          Assignee: unassigned at sourceware dot org
          Reporter: ncopa at alpinelinux dot org
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

After elfutils was updated to 0.190, iproute2 fails to build with this error:

In file included from bpf_legacy.c:24:
/usr/include/gelf.h:86:9: error: unknown type name 'Elf64_Relr'
   86 | typedef Elf64_Relr GElf_Relr;
      |         ^~~~~~~~~~


This appears to introduced with
https://sourceware.org/git/?p=elfutils.git;a=commit;h=39f2c500542f69c2f1a13fd0ae4eaa5778d2ed8d
which assumes that Elf64_Relr is typedef'ed if SHT_RELR is defined. This is not
(yet) the case in musl libc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-12-21  0:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-06 11:43 [Bug libelf/31034] New: iproute2 fails to build with elfutils 0.190 with musl libc ncopa at alpinelinux dot org
2023-11-06 11:50 ` [Bug libelf/31034] " ncopa at alpinelinux dot org
2023-12-21  0:55 ` mark at klomp dot org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).