[BUILD] superbuild tcl no such file

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[BUILD] superbuild tcl no such file

Hugues Fontenelle

Hello Slicer users!

 

I have one error in superbuild, described in [1].

My [2] and [3] are just things that I am curious about.

Thank you so much for your time; any help is greatly appreciated.

 

--

[1] I'm trying to build Slicer3 on Windows 7. I followed the instructions at

http://www.slicer.org/slicerWiki/index.php/Slicer3:Build_Instructions_Windows#Installing_Cygwin

(cygwin was installed with cvs,subversion,tcltk,unzip,zip; MSVC2008;

I ran CYGWIN as admin and navigated till the correct directory, then ran the script and got:

 

    $ ./Slicer3-svn/Scripts/getbuildtest.tcl

    couldn't read file "./Slicer3-svn/Scripts/getbuildtest.tcl": no such file or directory

 

Obviously I am sure that the file exists and I gave it 777 permission.

 

The beginning of the tcl file's content is:

 

    #!/bin/sh

    # the next line restarts using tclsh \

    exec tclsh "$0" "$@"

 

So I tried commenting out line 3 and running directly

 

    $ tclsh ./Slicer3-svn/Scripts/getbuildtest.tcl

 

but got the same error.

Any idea?

 

[2] By the way, the reason I want to rebuild all is to have a faster Slicer. The precompiled binaries are a bit slow so I suspect that they were built with some debug flags. Am I right?

 

[3] I have ITK, VTK, Qt, OpenCV, etc all build for my platform with MSVS2008 and Cmake 2.8.3. Could I build Slicer3 with those tools as well? Or is it that the libraries were patched and that the ones I have are unusable?

 

--

Warm regards

 

Hugues

 


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject
Reply | Threaded
Open this post in threaded view
|

Re: [BUILD] superbuild tcl no such file

inorton
Hi Hugues,

    $ ./Slicer3-svn/Scripts/getbuildtest.tcl

    couldn't read file "./Slicer3-svn/Scripts/getbuildtest.tcl": no such file or directory


What is the output from 'ls -la ./Slicer3-svn/Scripts/getbuildtest.tcl' ? Have you tried running ./getbuildtest from directly within the Scripts directory? (it will figure out the lib/build paths)

By the way, the reason I want to rebuild all is to have a faster Slicer. The precompiled binaries are a bit slow so I suspect that they were built with some debug flags. Am I right?

The precompiled binaries are built in release mode. For me the gui tends to be rather sluggish on Windows, and the rendering seems faster (anecdotal, non-scientific, vs. linux) This is all very dependent on your hardware.

I have ITK, VTK, Qt, OpenCV, etc all build for my platform with MSVS2008 and Cmake 2.8.3. Could I build Slicer3 with those tools as well? Or is it that the libraries were patched and that the ones I have are unusable?

The ITK and VTK versions are controlled by slicer_variables.tcl in ./Slicer3-svn. The checkout urls are in Scipts/genlib.tcl. Right now I think ITK is 3.20 from kitware but VTK is patched. OpenCV is not used, and Qt is optional in Slicer3

(if you want to use Qt or are starting from scratch and plan to do new development then you could consider Slicer4. it's not feature-complete for users yet, so Slicer3 is still the recommended version).

cheers,
-Isaiah


On Fri, May 20, 2011 at 9:02 AM, Hugues Fontenelle <[hidden email]> wrote:

Hello Slicer users!

 


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject
Reply | Threaded
Open this post in threaded view
|

Re: [BUILD] superbuild tcl no such file

Steve Pieper
Hi Hugues - also, I think the source directory needs to be named Slicer3 not Slicer3-svn for everything to work right.

-Steve

On Fri, May 20, 2011 at 10:48 AM, Isaiah Norton <[hidden email]> wrote:
Hi Hugues,


    $ ./Slicer3-svn/Scripts/getbuildtest.tcl

    couldn't read file "./Slicer3-svn/Scripts/getbuildtest.tcl": no such file or directory


What is the output from 'ls -la ./Slicer3-svn/Scripts/getbuildtest.tcl' ? Have you tried running ./getbuildtest from directly within the Scripts directory? (it will figure out the lib/build paths)


By the way, the reason I want to rebuild all is to have a faster Slicer. The precompiled binaries are a bit slow so I suspect that they were built with some debug flags. Am I right?

The precompiled binaries are built in release mode. For me the gui tends to be rather sluggish on Windows, and the rendering seems faster (anecdotal, non-scientific, vs. linux) This is all very dependent on your hardware.

I have ITK, VTK, Qt, OpenCV, etc all build for my platform with MSVS2008 and Cmake 2.8.3. Could I build Slicer3 with those tools as well? Or is it that the libraries were patched and that the ones I have are unusable?

The ITK and VTK versions are controlled by slicer_variables.tcl in ./Slicer3-svn. The checkout urls are in Scipts/genlib.tcl. Right now I think ITK is 3.20 from kitware but VTK is patched. OpenCV is not used, and Qt is optional in Slicer3

(if you want to use Qt or are starting from scratch and plan to do new development then you could consider Slicer4. it's not feature-complete for users yet, so Slicer3 is still the recommended version).

cheers,
-Isaiah


On Fri, May 20, 2011 at 9:02 AM, Hugues Fontenelle <[hidden email]> wrote:

Hello Slicer users!

 


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject
Reply | Threaded
Open this post in threaded view
|

Re: [BUILD] superbuild tcl no such file

Hugues Fontenelle

Thank you Isaiah for the nice answer.

Also Steve for the suggestion.

 

I renamed my dir Slicer3 but had already chmod 777 my file. Results:

$ ls -la ./Slicer3 /Scripts/getbuildtest.tcl

-rwxrwxrwxrwx+ 1 Hugues None 24157 May 23 09:35 get buildtest.tcl

 

I ran the script from within the dir also. Output is the same:

$ ./Slicer3 /Scripts/getbuildtest.tcl

couldn’t read file “./Slicer3 /Scripts/getbuildtest.tcl”: no such file or directory

 

The first 3 lines of the tcl script are:

# !/bin/sh

# the next line restarts using tclsh \

exec tclsh "$0" "$@"

 

If I comment out line 3, then the script will be interpreted as TCL and not be reloaded as TCLSH. Output is then:

$ ./Slicer3/Scripts/getbuildtest.tcl

./Slicer3/Scripts/getbuildtest.tcl: line 25: proc: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 26: global: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 60: puts: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 61: syntax error near expected token ‘}’

Which are expected since the script really is TCLSH not TCL.

 

I tried replacing those 3 first lines by:

#!/usr/bin/env tclsh

or

#!/usr/bin/tclsh

But that did not help.

 

Running

$ tclsh

Gives me the prompt

%

 

It seems that it has to do with the shell.

More ideas?

 

Cheers

Hugues

 

Subject: Re: [slicer-users] [BUILD] superbuild tcl no such file

 

Hi Hugues - also, I think the source directory needs to be named Slicer3 not Slicer3-svn for everything to work right.

-Steve

On Fri, May 20, 2011 at 10:48 AM, Isaiah Norton <[hidden email]> wrote:

Hi Hugues,

 

    $ ./Slicer3-svn/Scripts/getbuildtest.tcl

    couldn't read file "./Slicer3-svn/Scripts/getbuildtest.tcl": no such file or directory

 

What is the output from 'ls -la ./Slicer3-svn/Scripts/getbuildtest.tcl' ? Have you tried running ./getbuildtest from directly within the Scripts directory? (it will figure out the lib/build paths)

 

By the way, the reason I want to rebuild all is to have a faster Slicer. The precompiled binaries are a bit slow so I suspect that they were built with some debug flags. Am I right?


The precompiled binaries are built in release mode. For me the gui tends to be rather sluggish on Windows, and the rendering seems faster (anecdotal, non-scientific, vs. linux) This is all very dependent on your hardware.

 

I have ITK, VTK, Qt, OpenCV, etc all build for my platform with MSVS2008 and Cmake 2.8.3. Could I build Slicer3 with those tools as well? Or is it that the libraries were patched and that the ones I have are unusable?


The ITK and VTK versions are controlled by slicer_variables.tcl in ./Slicer3-svn. The checkout urls are in Scipts/genlib.tcl. Right now I think ITK is 3.20 from kitware but VTK is patched. OpenCV is not used, and Qt is optional in Slicer3

(if you want to use Qt or are starting from scratch and plan to do new development then you could consider Slicer4. it's not feature-complete for users yet, so Slicer3 is still the recommended version).

cheers,
-Isaiah

 

On Fri, May 20, 2011 at 9:02 AM, Hugues Fontenelle <[hidden email]> wrote:


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject
Reply | Threaded
Open this post in threaded view
|

Re: [BUILD] superbuild tcl no such file

inorton
In reply to this post by Steve Pieper
Hi,
 

I ran the script from within the dir also. Output is the same:

$ ./Slicer3 /Scripts/getbuildtest.tcl

couldn’t read file “./Slicer3 /Scripts/getbuildtest.tcl”: no such file or directory


Maybe it is just email formatting, but it seems there is a space in your path - though this does not appear in the later lines.

the exact path should be /Slicer3/Scripts/getbuildtest.tcl     --with no spaces.

if the path is correct, try this:
 
$ cd Slicer3/Scripts
$ ./getbuildtest.tcl

and:
$ tclsh ./getbuildtest.tcl

Also, if you happened to use a non-cygwin svn client, it may be fruitful to do a clean checkout using cygwin svn (be sure to use "Slicer3" as the base name). the  Windows/Cygwin setup is very sensitive to cases, paths, permissions, line endings, etc. so all build-related work should be done within cygwin bash shell.

-Isaiah

 

On Mon, May 23, 2011 at 3:54 AM, Hugues Fontenelle <[hidden email]> wrote:

Thank you Isaiah for the nice answer.

Also Steve for the suggestion.

 

I renamed my dir Slicer3 but had already chmod 777 my file. Results:

$ ls -la ./Slicer3 /Scripts/getbuildtest.tcl

-rwxrwxrwxrwx+ 1 Hugues None 24157 May 23 09:35 get buildtest.tcl

 

I ran the script from within the dir also. Output is the same:

$ ./Slicer3 /Scripts/getbuildtest.tcl

couldn’t read file “./Slicer3 /Scripts/getbuildtest.tcl”: no such file or directory

 

The first 3 lines of the tcl script are:

# !/bin/sh

# the next line restarts using tclsh \

exec tclsh "$0" "$@"

 

If I comment out line 3, then the script will be interpreted as TCL and not be reloaded as TCLSH. Output is then:

$ ./Slicer3/Scripts/getbuildtest.tcl

./Slicer3/Scripts/getbuildtest.tcl: line 25: proc: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 26: global: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 60: puts: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 61: syntax error near expected token ‘}’

Which are expected since the script really is TCLSH not TCL.

 

I tried replacing those 3 first lines by:

#!/usr/bin/env tclsh

or

#!/usr/bin/tclsh

But that did not help.

 

Running

$ tclsh

Gives me the prompt

%

 

It seems that it has to do with the shell.

More ideas?

 

Cheers

Hugues

 

Subject: Re: [slicer-users] [BUILD] superbuild tcl no such file

 

Hi Hugues - also, I think the source directory needs to be named Slicer3 not Slicer3-svn for everything to work right.

-Steve

On Fri, May 20, 2011 at 10:48 AM, Isaiah Norton <[hidden email]> wrote:

Hi Hugues,

 

    $ ./Slicer3-svn/Scripts/getbuildtest.tcl

    couldn't read file "./Slicer3-svn/Scripts/getbuildtest.tcl": no such file or directory

 

What is the output from 'ls -la ./Slicer3-svn/Scripts/getbuildtest.tcl' ? Have you tried running ./getbuildtest from directly within the Scripts directory? (it will figure out the lib/build paths)

 

By the way, the reason I want to rebuild all is to have a faster Slicer. The precompiled binaries are a bit slow so I suspect that they were built with some debug flags. Am I right?


The precompiled binaries are built in release mode. For me the gui tends to be rather sluggish on Windows, and the rendering seems faster (anecdotal, non-scientific, vs. linux) This is all very dependent on your hardware.

 

I have ITK, VTK, Qt, OpenCV, etc all build for my platform with MSVS2008 and Cmake 2.8.3. Could I build Slicer3 with those tools as well? Or is it that the libraries were patched and that the ones I have are unusable?


The ITK and VTK versions are controlled by slicer_variables.tcl in ./Slicer3-svn. The checkout urls are in Scipts/genlib.tcl. Right now I think ITK is 3.20 from kitware but VTK is patched. OpenCV is not used, and Qt is optional in Slicer3

(if you want to use Qt or are starting from scratch and plan to do new development then you could consider Slicer4. it's not feature-complete for users yet, so Slicer3 is still the recommended version).

cheers,
-Isaiah

 

On Fri, May 20, 2011 at 9:02 AM, Hugues Fontenelle <[hidden email]> wrote:


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject
Reply | Threaded
Open this post in threaded view
|

Re: [BUILD] superbuild tcl no such file

inorton
Also, what does `which tclsh` say? it must be the cygwin version or else the unix-style paths and line-endings will not work (it's possible to call windows binaries over cygwin depending on the resolution order)

On Mon, May 23, 2011 at 10:42 AM, Isaiah Norton <[hidden email]> wrote:
Hi,
 

I ran the script from within the dir also. Output is the same:

$ ./Slicer3 /Scripts/getbuildtest.tcl

couldn’t read file “./Slicer3 /Scripts/getbuildtest.tcl”: no such file or directory


Maybe it is just email formatting, but it seems there is a space in your path - though this does not appear in the later lines.

the exact path should be /Slicer3/Scripts/getbuildtest.tcl     --with no spaces.

if the path is correct, try this:
 
$ cd Slicer3/Scripts
$ ./getbuildtest.tcl

and:
$ tclsh ./getbuildtest.tcl

Also, if you happened to use a non-cygwin svn client, it may be fruitful to do a clean checkout using cygwin svn (be sure to use "Slicer3" as the base name). the  Windows/Cygwin setup is very sensitive to cases, paths, permissions, line endings, etc. so all build-related work should be done within cygwin bash shell.

-Isaiah

 

On Mon, May 23, 2011 at 3:54 AM, Hugues Fontenelle <[hidden email]> wrote:

Thank you Isaiah for the nice answer.

Also Steve for the suggestion.

 

I renamed my dir Slicer3 but had already chmod 777 my file. Results:

$ ls -la ./Slicer3 /Scripts/getbuildtest.tcl

-rwxrwxrwxrwx+ 1 Hugues None 24157 May 23 09:35 get buildtest.tcl

 

I ran the script from within the dir also. Output is the same:

$ ./Slicer3 /Scripts/getbuildtest.tcl

couldn’t read file “./Slicer3 /Scripts/getbuildtest.tcl”: no such file or directory

 

The first 3 lines of the tcl script are:

# !/bin/sh

# the next line restarts using tclsh \

exec tclsh "$0" "$@"

 

If I comment out line 3, then the script will be interpreted as TCL and not be reloaded as TCLSH. Output is then:

$ ./Slicer3/Scripts/getbuildtest.tcl

./Slicer3/Scripts/getbuildtest.tcl: line 25: proc: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 26: global: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 60: puts: command not found

./Slicer3/Scripts/getbuildtest.tcl: line 61: syntax error near expected token ‘}’

Which are expected since the script really is TCLSH not TCL.

 

I tried replacing those 3 first lines by:

#!/usr/bin/env tclsh

or

#!/usr/bin/tclsh

But that did not help.

 

Running

$ tclsh

Gives me the prompt

%

 

It seems that it has to do with the shell.

More ideas?

 

Cheers

Hugues

 

Subject: Re: [slicer-users] [BUILD] superbuild tcl no such file

 

Hi Hugues - also, I think the source directory needs to be named Slicer3 not Slicer3-svn for everything to work right.

-Steve

On Fri, May 20, 2011 at 10:48 AM, Isaiah Norton <[hidden email]> wrote:

Hi Hugues,

 

    $ ./Slicer3-svn/Scripts/getbuildtest.tcl

    couldn't read file "./Slicer3-svn/Scripts/getbuildtest.tcl": no such file or directory

 

What is the output from 'ls -la ./Slicer3-svn/Scripts/getbuildtest.tcl' ? Have you tried running ./getbuildtest from directly within the Scripts directory? (it will figure out the lib/build paths)

 

By the way, the reason I want to rebuild all is to have a faster Slicer. The precompiled binaries are a bit slow so I suspect that they were built with some debug flags. Am I right?


The precompiled binaries are built in release mode. For me the gui tends to be rather sluggish on Windows, and the rendering seems faster (anecdotal, non-scientific, vs. linux) This is all very dependent on your hardware.

 

I have ITK, VTK, Qt, OpenCV, etc all build for my platform with MSVS2008 and Cmake 2.8.3. Could I build Slicer3 with those tools as well? Or is it that the libraries were patched and that the ones I have are unusable?


The ITK and VTK versions are controlled by slicer_variables.tcl in ./Slicer3-svn. The checkout urls are in Scipts/genlib.tcl. Right now I think ITK is 3.20 from kitware but VTK is patched. OpenCV is not used, and Qt is optional in Slicer3

(if you want to use Qt or are starting from scratch and plan to do new development then you could consider Slicer4. it's not feature-complete for users yet, so Slicer3 is still the recommended version).

cheers,
-Isaiah

 

On Fri, May 20, 2011 at 9:02 AM, Hugues Fontenelle <[hidden email]> wrote:


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject



_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject
Reply | Threaded
Open this post in threaded view
|

Re: [BUILD] superbuild tcl no such file

Hugues Fontenelle

Hello

I found a solution for a problem that I described earlier. I have found a workaround and here is the summary.

 

Description of the bug:

The issue was that the TCL script appeared to “not exist”.

$ ./Slicer3/Scripts/getbuildtest.tcl

couldn’t read file “./Slicer3 /Scripts/getbuildtest.tcl”: no such file or directory

The file getbuildtest.tcl obviously exists and has the required permissions.

 

Solution:

As far as I understand, the problem is that the CYGWIN implementation of TCLSH does not resolve the window path properly.

I moved the script elsewhere and it worked.

 

Details:

My script path, on windows is:

C:\Users\Hugues\Documents\DEV\LIB\Slicer\Slicer3\Scripts

My script path, seen from cygwin is:

$ pwd

/cygdrive/c/Documents and Settings/Hugues/My Documents/DEV/LIB/Slicer/Slicer3/Scripts

My script path, seen from the tclsh shell, is:

$ tclsh

% pwd

C:/Documents and Settings//My Documents//LIB/Slicer/Slicer3/Scripts

(note the double // and missing directories)

I moved the Slicer3 in

C:\cygwin\home\Hugues\src\Slicer3

 

I’d be happy if anybody has a more technical description to the problem/solution, but in the meantime, this works J

 

Best regards to all,

 

Hugues


_______________________________________________
slicer-users mailing list
[hidden email]
http://massmail.spl.harvard.edu/mailman/listinfo/slicer-users
To unsubscribe: send email to [hidden email] with unsubscribe as the subject