From: "yuri at tsoft dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29092] error: failed to find _obstack_free
Date: Tue, 26 Apr 2022 17:39:32 +0000 [thread overview]
Message-ID: <bug-29092-10460-bvk4yTdGLa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29092-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29092
--- Comment #2 from yuri at tsoft dot com ---
(In reply to Mark Wielaard from comment #1)
> This isn't a new check, it has been there since 0.183.
> If your libc doesn't provide obstack support you probably have to provide a
> library that does to configure. What does config.log say precisely?
>
> See also
> https://sourceware.org/pipermail/elfutils-devel/2020q4/thread.html#3057
The previous version ported to FreeBSD was 0.179 and it didn't have such check
in configure.
Sources of obstack* functions are provided by the gnulib package but they
aren't built in that package - the sources are added to Makefile.am files here.
I had to remove the obstack configure check to make it pass.
---------------
Could you please make sure that elfutils builds on FreeBSD with clang?
Currently there are too many loose ends with elfutils.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-26 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 15:40 [Bug general/29092] New: " yuri at tsoft dot com
2022-04-26 17:08 ` [Bug general/29092] " mark at klomp dot org
2022-04-26 17:39 ` yuri at tsoft dot com [this message]
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-bvk4yTdGLa@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).