[Insight-developers] Problem again in NRRDIO

Michel Audette michel.audette at kitware.com
Thu Mar 25 15:52:36 EDT 2010


Hi Gordon.

Okay, will do.

I can get to this in a couple hours, and can send Daniel another header
file.

Best wishes,

Michel

On Thu, Mar 25, 2010 at 12:04 PM, Gordon L. Kindlmann <glk at uchicago.edu>wrote:

> Hi,
>
> I'm not an expert on parsing the output of nm, but I can say that these
> types of lines should not be appearing in a name-mangler header file,
> because "_airSanity.6121" is not a symbol that NrrdIO defines; "airSanity"
> is.  There is lots of information in the nm output that isn't relevant for
> name-mangling, and we just need to find which information it actually is.
>  From Bill it sounds like there isn't a standard uniform automated procedure
> for this, which is why we're struggling a bit.
>
> Every nm implementation is different, and (I think) necessarily OS-specific
> in the finer details.  If Daniel has access to a comparable linux box that
> he'd be in a position to help figure out which letter codes (used by nm to
> identify the symbol type, and by mangle.pl on line 66) are the rights ones
> to avoid name clashes.  I'm not currently able to work on this except try to
> keep up with the emails.
>
> Certainly, you can rule out a symbol that ends with ".N" where N is some
> integer; I don't think that's legit C syntax for anything.  But if such
> lines are appearing at all, I think its because an overly large set of
> letter codes is being pulled out by mangle.pl, and that's really the
> problem that needs fixing.
>
> Gordon
>
>
> On Mar 25, 2010, at 1:36 PM, Michel Audette wrote:
>
>  Gordon, can you interpret this error for me? Is this because of the .6121
>> and .8527?
>> #define _airSanity.6121 itk__airSanity.6121
>> #define _nrrdSanity.8527 itk__nrrdSanity.8527
>> ?
>> So what's need is a further check that no number occurs?
>>
>> If so, I can do that too...
>>
>> Michel
>>
>> On Thu, Mar 25, 2010 at 9:16 AM, Daniel Blezek <Blezek.Daniel at mayo.edu>
>> wrote:
>> My compiler didn’t like this line
>>
>> #define _airSanity.6121 itk__airSanity.6121
>>
>> [ 25%] Building C object Utilities/NrrdIO/CMakeFiles/ITKNrrdIO.dir/mop.o
>> In file included from
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/NrrdIO.h:59,
>>                 from
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/mop.c:25:
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/itk_NrrdIO_mangle.h:94:19:
>> warning: missing whitespace after the macro name
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/itk_NrrdIO_mangle.h:555:20:
>> warning: missing whitespace after the macro name
>> In file included from
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/NrrdIO.h:59,
>>                 from
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/754.c:25:
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/itk_NrrdIO_mangle.h:94:19:
>> warning: missing whitespace after the macro name
>> /Users/blezek/Source/Insight/Utilities/NrrdIO/itk_NrrdIO_mangle.h:555:20:
>> warning: missing whitespace after the macro name
>>
>>

-- 
Michel Audette, Ph.D.
R & D Engineer,
Kitware Inc.,
Chapel Hill, N.C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20100325/aea2a0bf/attachment.htm>


More information about the Insight-developers mailing list