From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 30654@debbugs.gnu.org
Subject: [bug#30654] giflib / khtml build failures
Date: Wed, 28 Feb 2018 21:16:46 +0100 [thread overview]
Message-ID: <0a80adad-2621-d2e6-3df9-5bab94471727@crazy-compilers.com> (raw)
In-Reply-To: <20180228201202.1481-1-h.goebel@crazy-compilers.com>
An example for these conflicts is building khtml:
In file included from /tmp/guix-build-khtml-5.39.0.drv-0/khtml-5.39.0/src/imload/decoders/gifloader.cpp:44:0:
/gnu/store/xs8cg35shfi5w32nqasz0nsmmf7wagmw-giflib-5.1.4/include/gif_lib.h:248:51: error: declaration of ‘void* reallocarray(void*, size_t, size_t)’ has a different exception specifier
reallocarray(void *optr, size_t nmemb, size_t size);
^
In file included from /gnu/store/cfdn69spjc44x4sd0acrwhxq6yay3rbc-gcc-5.5.0/include/c++/cstdlib:72:0,
from /gnu/store/cfdn69spjc44x4sd0acrwhxq6yay3rbc-gcc-5.5.0/include/c++/bits/stl_algo.h:59,
from /gnu/store/cfdn69spjc44x4sd0acrwhxq6yay3rbc-gcc-5.5.0/include/c++/algorithm:62,
from /gnu/store/cf9jagd5abi2wpsvd0bxa90i6d6npmba-qtbase-5.9.4/include/qt5/QtCore/qglobal.h:109,
from /gnu/store/cf9jagd5abi2wpsvd0bxa90i6d6npmba-qtbase-5.9.4/include/qt5/QtCore/qatomic.h:41,
from /gnu/store/cf9jagd5abi2wpsvd0bxa90i6d6npmba-qtbase-5.9.4/include/qt5/QtCore/qrefcount.h:43,
from /gnu/store/cf9jagd5abi2wpsvd0bxa90i6d6npmba-qtbase-5.9.4/include/qt5/QtCore/qbytearray.h:44,
from /gnu/store/cf9jagd5abi2wpsvd0bxa90i6d6npmba-qtbase-5.9.4/include/qt5/QtCore/QByteArray:1,
from /tmp/guix-build-khtml-5.39.0.drv-0/khtml-5.39.0/src/imload/imageloaderprovider.h:28,
from /tmp/guix-build-khtml-5.39.0.drv-0/khtml-5.39.0/src/imload/decoders/gifloader.h:4,
from /tmp/guix-build-khtml-5.39.0.drv-0/khtml-5.39.0/src/imload/decoders/gifloader.cpp:27:
/gnu/store/n6acaivs0jwiwpidjr551dhdni5kgpcr-glibc-2.26.105-g0890d5379c/include/stdlib.h:443:14: error: from previous declaration ‘void* reallocarray(void*, size_t, size_t) throw ()’
extern void *reallocarray (void *__ptr, size_t __nmemb, size_t __size)
^
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2018-02-28 20:17 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 ` Hartmut Goebel [this message]
2018-02-28 21:57 ` [bug#30654] giflib / khtml build failures Danny Milosavljevic
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=0a80adad-2621-d2e6-3df9-5bab94471727@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=30654@debbugs.gnu.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.
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).