Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 266653 - dev-libs/libxml2-2.7.3 macro conflicts with wxGTK
Summary: dev-libs/libxml2-2.7.3 macro conflicts with wxGTK
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
: 280974 (view as bug list)
Depends on:
Blocks: 264176
  Show dependency tree
 
Reported: 2009-04-18 14:55 UTC by Jose Luis Rivero (yoswink) (RETIRED)
Modified: 2009-08-13 22:34 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
printf macro renaming (libxml2-2.7.3-printf-rename.patch,16.87 KB, patch)
2009-04-18 14:57 UTC, Jose Luis Rivero (yoswink) (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jose Luis Rivero (yoswink) (RETIRED) gentoo-dev 2009-04-18 14:55:32 UTC
2.7.3 version of libxml2 includes ATTRIBUTE_PRINTF which is used by wxGTK generating a naming conflict when both libraries are used (see bug #264176).

Upstream has released a fix in SVN (see http://mail.gnome.org/archives/xml/2009-April/msg00021.html) but would be great to have the patch in portage as soon as posible to be able to compile again apps suffering this problem.

I picked up the diff from SVN and remove references to win32. It applies on 2.7.3 current portage version and tests pass just fine.

-r1 ebuild can be found at http://dev.gentoo.org/~yoswink/tmp/libxml2-2.7.3-r1.ebuild
Comment 1 Jose Luis Rivero (yoswink) (RETIRED) gentoo-dev 2009-04-18 14:57:02 UTC
Created attachment 188798 [details, diff]
printf macro renaming
Comment 2 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-04-27 21:23:25 UTC
in tree with 2.7.3-r1. Thanks for reporting and providing a patch.
Comment 3 Gilles Dartiguelongue (RETIRED) gentoo-dev 2009-08-13 22:34:18 UTC
*** Bug 280974 has been marked as a duplicate of this bug. ***