On Nov 24, 2008, at 12:54 PM, Ted Gould wrote:

On Mon, 2008-11-24 at 12:20 -0400, bulia byak wrote:

On Fri, Nov 21, 2008 at 11:48 PM, Ted Gould <ted@...11...> wrote:

I changed the autotools stuff a bit to be more flexible with other

compilers pulling an macro from the autotools macro archive.   I'll

commit it once SF starts talking to me again...

With my gcc 4.0.3, it fails as of rev 20254:

checking for OpenMP flag of C++ compiler... unknown

configure: error: Inkscape requires OpenMP support to build

Can't please make this an optional configure flag? I don't have

multiple cores and would like to avoid upgrading gcc on this machine,

as it would mean recompiling a ton of libraries.

We can of course, but I didn't because OpenMP was integrated into GCC

March 9, 2006[1] which was then released May 13, 2007[2].  And the GTK+

we're depending on 2.12 was released Fri, 14 Sep 2007[3].  It would seem

that if you had a new enough GTK+ you'd have a new enough GCC.

I guess my question here is that in this rather rare case is it worth

the complexity of having this, and likely more in the future, ifdefs in

the code?

Not a rare case.

On OS X, Apple is in charge of what compilers get bumped when. So the OpenMP stuff is failing at the moment.

I'm trying to make the config do the right thing and allow it to keep building here in Mac-land.