public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "doko at debian dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/27337] New: elfutils ftbfs on KFreeBSD and the Hurd
Date: Wed, 03 Feb 2021 14:43:28 +0000	[thread overview]
Message-ID: <bug-27337-10460@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27337
           Summary: elfutils ftbfs on KFreeBSD and the Hurd
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: general
          Assignee: unassigned at sourceware dot org
          Reporter: doko at debian dot org
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

seen with at least 0.182 on KFreeBSD and the Hurd:

[...]
        -Wl,--version-script,libelf.map,--no-undefined \
        -Wl,--whole-archive libelf_pic.a -Wl,--no-whole-archive \
        ../lib/libeu.a -lz 
/usr/bin/ld: libelf_pic.a(elf_update.os): in function `write_file':
./libelf/elf_update.c:109: undefined reference to `mremap'
collect2: error: ld returned 1 exit status
Makefile:1328: recipe for target 'libelf.so' failed
make[3]: *** [libelf.so] Error 1
Makefile:503: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
Makefile:419: recipe for target 'all' failed

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

             reply	other threads:[~2021-02-03 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 14:43 doko at debian dot org [this message]
2022-04-24 18:01 ` [Bug general/27337] " mark at klomp dot org
2022-07-01 21:25 ` mark at klomp dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27337-10460@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).