Comment 28 for bug 707205

Inkscape 0.48.2 (tarball) and 0.48.x (r9860) builds on OS X 10.7.2 Lion with attached patch applied to the sources - I haven't had the chance yet to verify the changes with Apple's GCC 4.2.1 nor with llvm-gcc-4.2. The patch seems save though:
1) AFAIU the older GCC version simply dropped the flag (before the changes for this bug) and it was not passed on to linker anyway.
2) Current trunk - which no longer uses the linker flag at all (bug #808338) - builds without issues using Apple's GCC 4.2.1 or llvm-gcc-4.2 as well as with GCC 4.6.2 [1].

The patch is based on the changes in trunk for bug #808338
<https://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/10437.1.2>

[1] The newer GCC version is installed via MacPorts, and also used to externally build and install all C++ interfaces Inkscape links to: libsigc++, glibmm, cairomm, pangomm, atkmm, gtkmm. Otherwise, using GCC 4.6 for Inkscape alone (for OpenMP support) results in unstable builds, similar to this topic described in the FAQ:
<http://wiki.inkscape.org/wiki/index.php/FAQ#On_Linux.2C_Inkscape_crashes_with_.22invalid_pointer.22_message>