[Insight-developers] SimpleITK : Dashboard errors: STL vector (long long)
Bradley Lowekamp
blowekamp at mail.nih.gov
Wed Jun 8 12:56:26 EDT 2011
Luis,
I push the topic to stage:
93-WrappingRuint64comp | master=0 next=0
When I enable R on my mac I get the following error:
[ 91%] Built target SimpleITKBasicFilters
make[2]: *** No rule to make target `Wrapping/CMakeFiles/SimpleITK.dir/depend'.
make[1]: *** [Wrapping/CMakeFiles/SimpleITK.dir/all] Error 2
This occurs both before and after the patch. So I was unable to determine if this corrected the issue, so I didn't merge it into next. Could you please test the topic and if it solves the issue merge it into next with:
$ ssh git at public.kitware.com stage SimpleITK merge -b next 93-WrappingRuint64comp
Thanks,
Brad
On Jun 8, 2011, at 11:27 AM, Luis Ibanez wrote:
> Brad,
>
>
> Certainly,
> Here is the corresponding issue:
>
> https://itk.icts.uiowa.edu/jira/browse/SIMPLEITK-93
>
>
> The SimpleITK Nightly build from "eldorado.kitware"
> has R wrapping enabled.
>
>
> Thanks
>
>
> Luis
>
> ----------------------------
> On Wed, Jun 8, 2011 at 11:21 AM, Bradley Lowekamp
> <blowekamp at mail.nih.gov> wrote:
>> 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
>>
>>
========================================================
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/d2af5ba5/attachment.htm>
More information about the Insight-developers
mailing list