After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 463285 - libart_lgpl/art_misc.h has been made unusable by C++ applications
libart_lgpl/art_misc.h has been made unusable by C++ applications
Status: RESOLVED DUPLICATE of bug 421299
Product: libart
Classification: Deprecated
Component: Other
2.3.17
Other All
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-03 22:58 UTC by Paul Davis
Modified: 2008-09-22 21:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paul Davis 2007-08-03 22:58:28 UTC
Steps to reproduce:
1. there is no crash, onloy the impossibility of compiling+linking C++ apps
2. bugzilla only seems to offer this silly simplistic form
3. a crash is the most severe classification i could find


Stack trace:


Other information:
some unthinking person converted art_alloc/art_free/art_realloc from macros into functions to provide win32 compatibility. but they didn't put these declarations inside the C++ extern "C" block of art_misc.h. as a result, any C++ application that links against libart_lgpl and uses this header and code that calls art_alloc() will fail to link because the linker cannot find the C++-mangled version of art_alloc(). 

this was reported to debian several months ago, it appears not to have been fed upstream.
Comment 1 Paul Davis 2007-08-03 23:00:46 UTC
this bug is not present in 2.3.17, but it is in 2.3.19, which is not listed in the  version dropdown for libart bug reports.
Comment 2 Daniel Macks 2007-09-10 05:34:46 UTC
Dup of Bug 421299 (among others) I think?
Comment 3 Paul Davis 2008-01-29 16:52:00 UTC
it is a duplicate and when the hell is this crippling and stupid problem going to be fixed? :)
Comment 4 Daniel Macks 2008-01-31 15:41:19 UTC
Fixed in 2.3.20 released on 30-Jan-2008
Comment 5 Sven Herzberg 2008-09-22 21:06:04 UTC
Closing, as dup (which is fixed).

*** This bug has been marked as a duplicate of 421299 ***