[Vv] Problems installing CLITK via vv superbuild file

Bilal Tahir b.tahir at sheffield.ac.uk
Wed Feb 27 15:22:43 CET 2013


Dear Vivien,

I deleted the previous version of vv and after installing and adding the
path, I got the following error:


[image: Inline images 1]

Please note that vv was working fine before and it didn't give this error.
Do you know how to solve it?

Best wishes,

Bilal

On 27 February 2013 13:51, Vivien Delmon <vivien.delmon at creatis.insa-lyon.fr
> wrote:

> On 02/24/2013 12:09 PM, Simon Rit wrote:
>
>> Dear Bilal,
>> We are considering this for VV first but we will not support this for
>> clitk tools. We are happy to provide clitk tools but users must try to
>> solve their compilation issues.
>>
>
> I just compiled the first vv nightly build (linux 64 bits) which is
> available here :
> http://www.creatis.insa-lyon.**fr/~delmon/vv_nightly/vv-**20130227.sh<http://www.creatis.insa-lyon.fr/~delmon/vv_nightly/vv-20130227.sh>
>
>  By the way, compilation of clitk tools, if this is what you are
>> interested in, should not require qt if you disable VV compilation
>> (CLITK_BUILD_VV:BOOL=OFF).
>> Simon
>>
>> On Sat, Feb 23, 2013 at 12:13 AM, Bilal Tahir <b.tahir at sheffield.ac.uk
>> <mailto:b.tahir at sheffield.ac.**uk <b.tahir at sheffield.ac.uk>>> wrote:
>>
>>     Can I make a request that the latest version of VV including CLITK
>>     with all options set to ON be made available as a precompiled .sh
>>     binary file? Slicer3D http://download.slicer.org/ allows for a
>>     nightly download of the binary version of the latest version.
>>
>>     This is due to my case where I have experienced many errors in
>>     trying to install the relevant programs until I finally get to
>>     install CLITK whereas the Oct 2012 precomiled binary .sh file worked
>>     fine on linux for me. However, CLITK was not included in that release.
>>
>>     Best wishes,
>>
>>     Bilal
>>
>>     On 22 February 2013 22:58, Bilal Tahir <b.tahir at sheffield.ac.uk
>>     <mailto:b.tahir at sheffield.ac.**uk <b.tahir at sheffield.ac.uk>>> wrote:
>>
>>         Dear All,
>>
>>         I am trying to install CLITK by adding the relevant =ON options
>>         on the CMakeLists.txt file (attached edited version in this
>>         email) found in the following link
>>         https://git.creatis.insa-lyon.**fr/pubgit/?p=clitk.git;a=blob;**
>> f=superbuild/CMakeLists.txt<https://git.creatis.insa-lyon.fr/pubgit/?p=clitk.git;a=blob;f=superbuild/CMakeLists.txt>
>>
>>         I then run the following two commands:
>>
>>
>>         cmake superbuild-file-directory
>>         make
>>
>>         However, after running 'make' it started installing the programs
>>         (ITK, QT and VTK) one after the other for several hours until it
>>         reached 60% of the last program 'VV' where it gave the following
>>         errors and stopped:
>>
>>         collect2: ld returned 1 exit status
>>         make[5]: *** [bin/vv] Error 1
>>         make[4]: *** [vv/CMakeFiles/vv.dir/all] Error 2
>>         make[3]: *** [all] Error 2
>>         make[2]: *** [Stamp/VV/VV-build] Error 2
>>         make[1]: *** [CMakeFiles/VV.dir/all] Error 2
>>         make: *** [all] Error 2
>>
>>         I've copied and posted some of the last few lines up till the
>>         point that the error came.
>>
>>         The 'make' command created several folders in my home folder
>>         (/home/md1bat/) including 'Source' and 'Build'. It appears that
>>         ITK, QT and VTK (not VV) completed as you can see from
>>         the /home/md1bat/CMakeFiles/ folder.
>>
>>         Inline images 1
>>
>>         Within the 'Build' folder, each of the four programs, ITK, VTK,
>>         QT and VV have at least a bin and/or lib folder. This is not the
>>         case in the 'Source' folder. Therefore, I have added the paths
>>         of the respective bin and lib folders from the 'Build' folder
>>         (not Source) to my .bashrc file (attached in this email).
>>         However, none of the programs (including the completed ITK, QT
>>         and VTK) seem to work even if I want to check which version I
>>         have installed using the command e.g itk --version. I have now
>>         deleted the precompiled 'VV' Oct 2012 version which used to work
>>         with the command vv. However, the command vv now gives the
>>         output 'command not found'.
>>
>>         I'm not sure if I have done the export path correctly on my
>>         .bashrc as I have referenced it to the 'Build' folder and not
>>         the 'Source' folder as there was no bin or lib folders within
>>         that. Furthermore, I have no idea why the errors occurred.
>>
>>         Please let me know if you have any suggestions.
>>
>>         Best wishes,
>>
>>         Bilal Tahir,
>>         James Morrison Researcher in Radiotherapy Imaging,
>>         University of Sheffield/Weston Park Cancer Hospital
>>
>
> --
> Vivien Delmon
> PhD student at CREATIS, Lyon
> Supported by ANRT and ELEKTA
> http://www.creatis.insa-lyon.**fr/rio<http://www.creatis.insa-lyon.fr/rio>
>
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> ______________________________**_________________
> vv mailing list
> vv at creatis.insa-lyon.fr
> http://www.creatis.insa-lyon.**fr/mailman/listinfo/vv<http://www.creatis.insa-lyon.fr/mailman/listinfo/vv>
>



-- 
Bilal Tahir,
James Morrison Researcher in Radiotherapy Imaging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.creatis.insa-lyon.fr/pipermail/vv/attachments/20130227/d3688f17/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 13027 bytes
Desc: not available
URL: <http://www.creatis.insa-lyon.fr/pipermail/vv/attachments/20130227/d3688f17/attachment-0001.png>


More information about the vv mailing list