From: "yuri at tsoft dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29092] New: error: failed to find _obstack_free
Date: Tue, 26 Apr 2022 15:40:31 +0000 [thread overview]
Message-ID: <bug-29092-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29092
Bug ID: 29092
Summary: error: failed to find _obstack_free
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: yuri at tsoft dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
On FreeBSD 13 version 0.187 fails to configure:
> checking for library containing _obstack_free... no
> configure: error: in `/disk-samsung/freebsd-ports/devel/elfutils/work/elfutils-0.187':
> configure: error: failed to find _obstack_free
> See `config.log' for more details
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-04-26 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 15:40 yuri at tsoft dot com [this message]
2022-04-26 17:08 ` [Bug general/29092] " mark at klomp dot org
2022-04-26 17:39 ` yuri at tsoft dot com
2022-04-26 17:46 ` 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-29092-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).