[Insight-developers] SimpleITK : Dashboard errors: STL vector (long long)
Bradley Lowekamp
blowekamp at mail.nih.gov
Wed Jun 8 11:21:28 EDT 2011
Luis,
Thanks for submitting the experimental:
http://www.cdash.org/CDash/viewBuildError.php?buildid=1212065
These error messages say that it's related to R. There were a few different changes made to related to the uint64 issue. Since your system was the only one building R, I guess the change didn't make it into the R swig related code.
R is being very much neglected as we don't even have a Wrapping/R.i file for R specific customizations.
Can you please create a JIRA issue and assign it to me? I think I know where the problem is, so I will create a topic.
Brad
On Jun 8, 2011, at 11:10 AM, Luis Ibanez wrote:
> Hi Brad,
>
> After rebuilding SimpleITK from scratch,
> it looks like some of the compilation errors
> that we are getting in the Dashboard are real
> and they are related to converting:
>
> std::vector<long unsigned int, std::allocator<long unsigned int> >*’
>
> to
>
> std::vector<long long unsigned int, std::allocator<long long unsigned int> >*’
>
> in
>
> SWIGINTERN std::vector< unsigned long long,std::allocator< unsigned
> long long > > *std_vector_Sl_uint64_t_Sg____getslice__(std::vector<
> uint64_t > *self,std::vector< unsigned long long >::difference_type
> i,std::vector< unsigned long long >::difference_type j){
> return swig::getslice(self, i, j);
>
>
> This is in a 64bits Linux machine.
>
> It would seem that we may be mixing "long" and "long long"
> types when wrapping STL vectors for R.
>
>
> Any hints on where did we introduced this problem ?
>
>
> Luis
========================================================
Bradley Lowekamp
Lockheed Martin Contractor for
Office of High Performance Computing and Communications
National Library of Medicine
blowekamp at mail.nih.gov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20110608/8aff8d37/attachment.htm>
More information about the Insight-developers
mailing list