On 21/05/06, Jon A. Cruz <jon@...18...> wrote:
On May 21, 2006, at 7:27 AM, Ben Fowler wrote: [ snip ]
I suspect that people sucessfully compiling Inkscape are using their own sigc++ and installing it in /usr/local or some other prefix that is searched before /sw. This does in fact, work for me. I will update the page now, with this info, but we really need some guidance for what advice to give to Mac devs who have been relying on fink.
No.
The problem is that sigc++ 2.0.12 is *only* a problem with gcc 4.0.x
The default for fink is gcc 3.3, which works *fine* with sigc++ 2.0.11
So the dependency on ">= 2.0.12" is only if gcc is also 4.0.x.
Anyone pulling things from fink and doing a straight build will be able to as long as they follow fink's default of using gcc 3.3.
Thanks Jon, I have updated the Wiki. It would be good if the OP could review this info and report whether it solves the immediate problem.
Do we know if the svn configure.ac handles the various cases: Tiger/Panther gcc 3/gcc 4? I was under the impression that under Panther the later sigc++ was being requested, but this info may be out of date, or simply wrong.
I am just spinning Inkscape again (r11885)
Ben
Ben.