From: Danny Milosavljevic <dannym@scratchpost.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 30654@debbugs.gnu.org
Subject: [bug#30654] giflib / khtml build failures
Date: Wed, 28 Feb 2018 22:57:42 +0100 [thread overview]
Message-ID: <20180228225742.77c7707e@scratchpost.org> (raw)
In-Reply-To: <0a80adad-2621-d2e6-3df9-5bab94471727@crazy-compilers.com>
Hi Harmut,
I would prefer to remove reallocarray from giflib entirely.
As it is now, it's anyone's guess which of the functions is taken after ld.so is
done with setting up your program-using-glibc-and-giflib (I'm sure there's
a resolution mechanism but let's not tempt it to fail please).
I'd just empty giflib's lib/openbsd-reallocarray.c and remove the prototype
from the header file entirely.
/gnu/store$ objdump -t ywvngg36v2cdidcclvk0k14mxmmn73wp-giflib-5.1.4/lib/libgif.so.7 |grep reallocarray
0000000000005970 g F .text 0000000000000056 reallocarray
That means giflib and glibc both define the same function with mutually
incompatible signatures (here only slightly incompatible).
Note that this is only a problem for C++ since C doesn't have exceptions.
next prev parent reply other threads:[~2018-02-28 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 20:12 [bug#30654] [PATCH 1/1] gnu: giflib: Make "reallocarray" private, solve glibc@2.26 conflict Hartmut Goebel
2018-02-28 20:16 ` [bug#30654] giflib / khtml build failures Hartmut Goebel
2018-02-28 21:57 ` Danny Milosavljevic [this message]
2018-02-28 21:06 ` Hartmut Goebel
2018-02-28 22:18 ` Danny Milosavljevic
2018-02-28 22:10 ` Danny Milosavljevic
2018-02-28 21:46 ` [bug#30654] [PATCH v2 1/1] gnu: giflib: Make "reallocarray" private, solve glibc@2.26 conflict Hartmut Goebel
2018-03-01 4:01 ` Danny Milosavljevic
2018-03-01 7:52 ` Hartmut Goebel
2018-03-17 17:29 ` Manolis Ragkousis
2018-03-17 20:58 ` Hartmut Goebel
2018-06-22 15:37 ` bug#30654: " Gábor Boskovits
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180228225742.77c7707e@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30654@debbugs.gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).