[Pythonmac-SIG] Configure question

[Doug Wyatt]

Aha, it turns out that I don't have to force use of g++, just tweak 
XIST's setup.py, e.g.:

	Extension("ll.xist.csstokenizer", ["_xist/csstokenizer.cxx"], 
extra_link_args=['-lstdc++']),

I imagine there's a more broad/elegant solution... but I'm just trying 
this out...

Doug


On Friday, Dec 13, 2002, at 22:54 US/Pacific, Doug Wyatt wrote:

> I'm trying to build XIST (www.livinglogic.de) which has a Python 
> extension module written in C++.  I get this same link error.
>
> I've looked around the way configure works just a little... it seems 
> that g++ (or c++) must be used as the linker when the source file is 
> c++, but it looks like configure, even if supplied --with-cxx=c++, 
> doesn't result in LINKCC being defined as c++ -- or there being any 
> conditional rules for using a C++ link command (c++ -libstdc++) when 
> necessary.
>
> Since XIST uses setup.py, it isn't immediately obvious how to 
> special-case the way it's built...
>
> Any thoughts?
>
> TIA,
> Doug
>
>
> On Saturday, Aug 31, 2002, at 14:23 US/Pacific, bill fancher wrote:
>> I'm running 10.2 and upgraded autoconf to 2.53 so that I can 
>> regenerate configure from configure.in. Having done so, I now notice 
>> that I get the following line in configure output:
>>
>> checking LINKCC... ld: Undefined symbols:
>> ___gxx_personality_v0
>>
>> Should I worry? Is it just something I overlooked before? Is anyone 
>> else seeing this? (He asked, hoping to avoid having to isolate, and 
>> perhaps remedy, the underlying cause.)
>>
> --
> Doug Wyatt
> doug@sonosphere.com
> http://www.sonosphere.com/
>