Fw: [Insight-users] Insight 1.6 Compilation

Brad King brad.king at kitware.com
Thu, 19 Feb 2004 13:49:38 -0500


Mauricio Inforçati wrote:
> Brad,
> Here it goes xml.log. It seems gcc is not using the "patch", isn´t it?

No, and it looks like the patched header is not installed by "make 
install".  I'll fix this, but to work-around the bug for now, change 
CableSwig_DIR in your ITK cmake cache to point at the CableSwig build tree.

-Brad

>  Thanks for instrutions,
>     Mauricio
> 
> 
>>----- Original Message ----- 
>>From: "Brad King" <brad.king at kitware.com>
>>To: "Mauricio Inforçati" <mauricio.inforcati at cenpra.gov.br>
>>Sent: Thursday, February 19, 2004 11:40 AM
>>Subject: Re: [Insight-users] Insight 1.6 Compilation
>>
>>
>>
>>>Mauricio Inforçati wrote:
>>>
>>>>I´ve got it on ITK download site, just below
> 
> insightToolkit-1.6.0.tar.gz
> 
>>>>link.  CableSwig-ITK-1.6.0.tar.gz
>>>
>>>Okay, that version should have the fix.  We'll have to track down why it
>>>didn't work.  The error message you are seeing is coming from GCC-XML
>>>within CableSwig.  It uses a patched parser from GCC 3.3 to parse C++
>>>code to help generate wrappers.  Part of doing this means that the GCC
>>>3.3 parser must handle the header files from your system's GCC 2.95
>>
>>library.
>>
>>>GCC-XML comes with a special set of headers written to wrap around GCC
>>>2.95's headers and make them parsable by 3.3.  Look in
>>>CableSwig/GCC_XML/Support/GCC/2.95 to see them.  In particular, there
>>>should be a pthread.h header present that looks like this:
>>>
>>>#ifndef GCCXML_PTHREAD_H
>>>#define GCCXML_PTHREAD_H
>>>
>>>/* Some pthread.h files use __thread, which is a keyword for GCC 3.3.
>>>    Change the name for the duration of including pthread.h.  */
>>>#ifndef __thread
>>># define __thread gccxml__thread
>>># define gccxml__thread gccxml__thread
>>>#endif
>>>#include_next <pthread.h>
>>>#ifdef gccxml__thread
>>># undef gccxml__thread
>>># undef __thread
>>>#endif
>>>
>>>#endif
>>>
>>>We need to determine whether this file is getting used and whether it is
>>>working.  Please go to Wrapping/CSwig/Common in your build tree and run
>>>
>>>make `pwd`/wrap_ITKCommonBase.xml VERBOSE=1 >xml.log 2>&1
>>>
>>>Then send me the xml.log file that is produced.
>>>
>>>Thanks,
>>>-Brad
>>>
>>>
>>