Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 230571 - libart_lgpl: art_alloc declaration causes c++ compilations (including kdelibs) to fail
libart_lgpl: art_alloc declaration causes c++ compilations (including kdelibs...
Product: Fedora
Classification: Fedora
Component: libart_lgpl (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Behdad Esfahbod
Depends On:
  Show dependency treegraph
Reported: 2007-03-01 11:32 EST by Rex Dieter
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-01 16:33:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rex Dieter 2007-03-01 11:32:08 EST
Recent versions of libart_lgpl changed the declarations of art_alloc, art_free,
art_realloc from #defines to real functions, but didn't wrap these with with 
extern "C", which can/will cause c++ apps that use libart to fail linking. The
following patch addresses that:

- libart_lgpl-2.3.19/art_misc.h.extern-c      2007-01-02 00:59:22.000000000 
+++ libart_lgpl-2.3.19/art_misc.h       2007-03-01 09:19:06.000000000 +0100
@@ -34,9 +34,15 @@
 #include <libart_lgpl/art_config.h>

+#ifdef __cplusplus
+extern "C" {
 void *art_alloc(size_t size);
 void art_free(void *ptr);
 void *art_realloc(void *ptr, size_t size);
+#ifdef __cplusplus
+#endif /* __cplusplus */
Comment 1 Rex Dieter 2007-03-01 11:53:10 EST
FYI, Just read on the kde-packager ml that this fix has already been applied
upstream, and will (presumably) be included in the next release.  Dunno how long
a new release will take though, so fixing this asap would be appreciated (since
it blocks kdelibs (re)builds).
Comment 2 Behdad Esfahbod 2007-03-01 16:33:04 EST
Building 2.3.19-2.

Note You need to log in before you can comment on or make changes to this bug.