chromatic via RT wrote:
Does this happen after a 'make realclean' and recompilation?
In fact, it only happened when I ran 'make realclean' and recompiled.
I'd been happily running 'make' with no problems. I was surprised to see
the error pop up on the pdd17pmc branch after I merged, so went back to
trunk and ran 'make realclean', and there it was.
You in particular know that I have a special dislike for the state of building
and linking C code on Mac OS X, being dangerously close to The Best That Unix
Had To Offer Circa NeXT 1987...
.. but apart from slapping PARROT_API on the symbol, what in the world do we
need to do special to tell GCC 4.x on Mac OS X to:
1) hide symbols not explicitly exported
2) actually export symbols when we mark them as exportable
I mean, the main reason we hide symbols by default is so that we'll catch what
would be compilation errors on Win32 on platforms with GCC 4.x, but if Mac OS
X can't handle a bog-standard compilation option, well maybe we should work
on getting them the source code to GCC or something.
Maybe I should try compiling on LLVM. ;)
Allison
