From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: wxSVGXML?
Date: Wed, 4 Jun 2008 17:06:45 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.06.04.17.06.44@cox.net> (raw)
In-Reply-To: 4846A91C.6010605@ercbroadband.org
"Mark Haney" <mhaney@ercbroadband.org> posted
4846A91C.6010605@ercbroadband.org, excerpted below, on Wed, 04 Jun 2008
10:39:24 -0400:
> Thanks to everyone for helping this ebuild n00b get working. I've get
> everything setup, but now I've hit a snag. The ebuild I am working on
> requires svgxml.h and I cannot find that file. With other distros it's
> in the wxsvg-devel package (or similar), but I can't find one for that
> in Gentoo. With wxsvg, there's a wxSVG and wxXML folder in
> /usr/include/, but neither have this file.
>
> I don't even know where to begin looking for it in Gentoo. Ideas?
I don't have the file and don't have any of the wxWidgets installed, but
at a guess... wrong version. This seems to be confirmed with a search:
Google this for the fedora 1.0 beta 10 package:
wxsvg-devel-1.0-0.8.b10 svgxml.h
Now replace the b10 with b9, b8, etc. No hits. Delete the svgxml.h bit
and you get hits again, so it's seeing the package, just not that file in
the package.
Therefore, it would seem that file was added in beta 10.
Unfortunately, Gentoo's tree is outdated, with only the beta 7 ebuild. A
quick check of bugzy results in:
media-libs/wxsvg-1.0_beta10 version bump request
http://bugs.gentoo.org/show_bug.cgi?id=215665
Seems they're working on it, but it needs some patches to work with
Gentoo, and while it's building, it isn't actually functional (segfaults).
So... you can try hacking that ebuild and see if you can get it to work,
or building and installing manually, to see if that works. I'd certainly
suggest CCing yourself to the bug.
It's also possible that whatever you are trying to build against that
header file, you can either find an older version that builds against
beta 7, or maybe, you can merge the building but segfaulting beta 10, and
not have it matter if all you need are the header files.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-04 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 14:39 [gentoo-amd64] wxSVGXML? Mark Haney
2008-06-04 14:50 ` Justin
2008-06-04 16:09 ` Sebastian Redl
2008-06-04 16:50 ` Mark Haney
2008-06-04 17:17 ` Drake Donahue
2008-06-04 17:06 ` Duncan [this message]
2008-06-04 17:44 ` [gentoo-amd64] wxSVGXML? Mark Haney
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2008.06.04.17.06.44@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox