The machine is an SGI Octane (R10K) running Irix 6.5.17 with MIPSpro 7.3
compilers and python 2.3.4 with numeric 23.1
SGI's OpenGL and glut just don't work well with python for some
reason. Therefore, I used the the ignore GL option for tk graphics
only.
X11 is in /usr
tcl8.3.5, tk 8.3.5, and python2.3.4 are all installed in /usr/local
The origin of the problem is that the libraries are all in the
default build directory of /usr/local/lib With prior versions
of installCode.py, this was not a problem. However, a consequence
of the update to installCode.py for 64 bit linux builds is that
on the SGI installCode.py creates an environment.txt that refers
to the nonexistent directory /usr/local/lib32 The scripts in
the bin directory created by installCode.py also refer to this
nonexistent directory, but the setenv statements in these scripts
are not executable because none of the scripts begins with the line
#!/bin/csh
Thus the scripts in bin give an error message about an unknown command
setenv for each of the setenv statements.
In order to build on SGI, I edited the environment.txt to change
all references from /usr/local/lib32 to /usr/local/lib
I also edited each of the scripts in bin the same way as well as
adding the line #!/bin/csh to each script to make them truly executable.
An alternative to the edit of library references would be to link
/usr/local/lib32 to /usr/local/lib
Messages on build were as follows:
>%python installCode.py analysis
>Messages will be logged in "log_Analysis_1.txt"
>Assuming your platform is irix
>Need to know where X11 directory is, in order to compile Analysis
>(This directory should contain [include/X11/Xlib.h, lib/libX11.*])
>Where is the X11 dir? /usr
>You have choice of installing provided Tcl8.3 or using already installed Tcl.
>Unpack Tcl8.3 (y or n)? n
>Compile and install Tcl8.3 (y or n)? n
>Need to know where Tcl directory is, in order to compile Analysis
>(This directory should contain [include/tcl.h, lib/tclConfig.sh])
>Where is the Tcl dir? /usr/local
>Guess Tcl/Tk version = 8.3 (by looking), is this ok (y or n) (reply y unless sure otherwise)? y
>You have choice of installing provided Tk8.3 or using already installed Tk.
>Unpack Tk8.3 (y or n)? n
>Compile and install Tk8.3 (y or n)? n
>Need to know where Tk directory is, in order to compile Analysis
>(This directory should contain [include/tk.h, lib/tkConfig.sh], and /usr/local does)
>Guess Tk dir = "/usr/local", is this correct (y or n)? y
>Assuming Tk version is also 8.3
>You have choice of installing provided Python2.4 or using already installed Python.
>It must be 2.4 or higher, and it must have Tcl/Tk compiled in (latter not checked here).
>Unpack Python2.4 (y or n)? n
>Compile and install Python2.4 (y or n)? n
>Need to know where Python directory is, in order to compile Analysis
>(This directory should contain [include/python2.*, lib/python2.*])
>Where is the Python dir? /usr/local
>Guess Python version = 2.3 (by looking), is this ok (y or n) (reply y unless sure otherwise)? y
>Are you using 64 bit libraries? (answer n unless you know otherwise) (y or n))? n
>Do you want OpenGL used in Analysis (y or n) (n means only get Tk)? n
>Compile and install Analysis code (y or n)? y
>You can create environment file from scratch (this does not copy it from environment_default.txt)
>If you have already created it and edited it by hand you probably do not want to create it again here.
>Create environment file (y or n) (answer y unless you know otherwise)? y
>Use -fPIC compiler flag (y or n) (if gcc compiler y, otherwise n; answer y unless you know otherwise)? n
> cd memops/global; make
> cc -c -I/usr/local/include/python2.3 -O -DDO_NOT_HAVE_MALLOC python_util.c
> cc -c -O -DDO_NOT_HAVE_MALLOC utility.c
> cc -c -O -DDO_NOT_HAVE_MALLOC hash_list.c
> cc -c -O -DDO_NOT_HAVE_MALLOC hash_table.c
> cc -c -O -DDO_NOT_HAVE_MALLOC mem_cache.c
> cc -c -O -DDO_NOT_HAVE_MALLOC mutex.c
> cc -c -I/usr/local/include/python2.3 -O -DDO_NOT_HAVE_MALLOC py_mem_cache.c
> cc -c -O -DDO_NOT_HAVE_MALLOC block_file.c
> cc -c -O -DDO_NOT_HAVE_MALLOC int_array.c
> cc -c -I/usr/local/include/python2.3 -O -DDO_NOT_HAVE_MALLOC py_block_file.c
> cc -shared -o BlockFile.so python_util.o utility.o hash_list.o hash_table.o mem_cache.o mutex.o py_mem_cache.o block_file.o int_array.o py_block_file.o
> cc -c -DIGNORE_GL -I/usr/local/include/python2.3 -I/usr/include -I/usr/local/include -I/usr/local/include -O -DDO_NOT_HAVE_MALLOC gl_handler.c
> cc -c -DIGNORE_GL -DUSE_GL_TRUE -I/usr/local/include/python2.3 -I/usr/include -I/usr/local/include -I/usr/local/include -O -DDO_NOT_HAVE_MALLOC py_gl_handler.c
> cc -shared -o GlHandler.so -L/usr/lib32 -L/usr/local/lib32 -L/usr/local/lib32 \
> python_util.o utility.o gl_handler.o py_gl_handler.o -ltk8.3 -ltcl8.3 -lX11 -lXext -lm
>ld32: FATAL 9 : I/O error (-ltk8.3): No such file or directory
>*** Error code 2 (bu21)
>*** Error code 1 (bu21)
>Cannot access *.so: No such file or directory
>Cannot access *.so: No such file or directory
>Cannot access *.so: No such file or directory
>Do you want to create a bin directory (answer y unless you know otherwise) (y or n)? n
>Run Analysis (as test) (y or n)? n
>Finished installation script
Sincerely,
--
Bruce D. Ray, Ph.D.
Associate Scientist, and Operations Director
NMR Center
IUPUI
Physics Dept.
402 N. Blackford St.
Indianapolis, IN 46202-3273
|
