<div dir="ltr">Thanks Jason. I have pinpointed the location of the error to a very specific gcc line. I am reproducing the error below (very easy to read):<div><br></div><div>I run:<br></div><div><div><br></div><div>==================================================================<br>
</div><div>export CPPFLAGS='-I/opt/sqlite-3.7.16.2/include -I/opt/tk8.6.0/include -I/opt/tcl8.6.0/include/'</div><div><br></div><div>export LDFLAGS='-L/opt/sqlite-3.7.16.2/lib -L/opt/tk8.6.0/lib/ -L/opt/tcl8.6.0/lib/ ./configure --prefix=/path_to_python-2.7.4 --enable-shared</div>
<div>==================================================================<br></div><div><br></div><div>and then I run make and I got the following:</div><div><br></div><div>==================================================================</div>
<div>....</div><div>building '_tkinter' extension </div><div><br></div><div>gcc -pthread -fPIC -fno-strict-aliasing</div><div>-g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -I/usr/X11/include -I. -IInclude -I./Include -I/opt/sqlite/sqlite-3.7.16.2/include -I/opt/tk8.6.0/include -I/opt/tcl8.6.0/include -I/usr/local/include -I/opt/python/src/Python-2.7.4/Include -I/opt/python/src/Python-2.7.4 -c /opt/python/src/Python-2.7.4/Modules/_tkinter.c -o build/temp.linux-x86_64-2.7/opt/python/src/Python-2.7.4/Modules/_tkinter.o</div>
<div><br></div><div>gcc -pthread -fPIC -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3</div><div>-Wall -Wstrict-prototypes -DWITH_APPINIT=1 -I/usr/X11/include -I. -IInclude -I./Include -I/opt/sqlite/sqlite-3.7.16.2/include -I/opt/tk8.6.0/include -I/opt/tcl8.6.0/include -I/usr/local/include -I/opt/python/src/Python-2.7.4/Include -I/opt/python/src/Python-2.7.4 -c /opt/python/src/Python-2.7.4/Modules/tkappinit.c -o build/temp.linux-x86_64-2.7/opt/python/src/Python-2.7.4/Modules/tkappinit.o</div>
<div><br></div><div>gcc -pthread -shared -L/opt/sqlite/sqlite-3.7.16.2/lib</div><div>-L/opt/tk8.6.0/lib/ -L/opt/tcl8.6.0/lib/ -L/opt/sqlite/sqlite-3.7.16.2/lib -L/opt/tk8.6.0/lib/ -L/opt/tcl8.6.0/lib/ -I. -IInclude -I./Include -I/opt/sqlite/sqlite-3.7.16.2/include -I/opt/tk8.6.0/include -I/opt/tcl8.6.0/include build/temp.linux-x86_64-2.7/opt/python/src/Python-2.7.4/Modules/_tkinter.o</div>
<div>build/temp.linux-x86_64-2.7/opt/python/src/Python-2.7.4/Modules/tkappinit.o</div><div>-L/usr/X11/lib -L/opt/sqlite/sqlite-3.7.16.2/lib -L/opt/tk8.6.0/lib/ -L/opt/tcl8.6.0/lib/ -L/usr/local/lib -L. -ltk8.6 -ltcl8.6 -lX11 -lpython2.7 -o build/lib.linux-x86_64-2.7/_tkinter.so</div>
<div><br></div><div>*** WARNING: renaming "_tkinter" since importing it failed: <a href="http://libtk8.6.so">libtk8.6.so</a>: cannot open shared object file: No such file or directory</div><div>...<br></div><div>
==================================================================<br></div><div><br></div><div>The odd thing is that I can see `<a href="http://libtk8.6.so">libtk8.6.so</a>` under /opt/tcl8.6.0/lib, as I specified with `LDFLAGS`:<br>
</div><div><br></div><div>==================================================================<br></div><div style>cd /opt/tcl8.6.0/lib</div><div style>ls</div><div style>. </div><div style>../ </div><div style>pkgconfig </div>
<div style>tk8.6 </div><div style>libtkstub8.6.a </div><div style>tkConfig.sh </div><div style><a href="http://libtk8.6.so">libtk8.6.so</a></div><div>==================================================================<br></div>
<div><br></div><div style>The file <a href="http://libtk8.6.so">libtk8.6.so</a> has 1.5M and is definitely there.</div><div style><br></div><div>So why did that compilation fail?</div><div><br></div><div style>James</div>
<div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 18, 2013 at 11:05 AM, Jason Swails <span dir="ltr"><<a href="mailto:jason.swails@gmail.com" target="_blank">jason.swails@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style><br></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">
On Thu, Apr 18, 2013 at 10:37 AM, James Jong <span dir="ltr"><<a href="mailto:ribonucleico@gmail.com" target="_blank">ribonucleico@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks so much Chris. This is part of a super computer and I am afraid I don't have access to a machine with sudo permissions and similar architecture & OS.<div>
<br></div><div>Is there any way to active higher level of verbosity during the build process to identify what is failing? Or anything specifically I should watch for?</div></div></blockquote><div><br></div></div><div style class="gmail_default">
Most supercomputers I'm familiar with have some variant of Linux running (e.g., SUSE or Red Hat are quite common). Some of these machines only have barebone kernels on the compute nodes, though, and have a fully-fledged Linux OS only on the login nodes... This info is typically on the website for that supercomputer (if it has one), or any other available documentation.</div>
<div style class="gmail_default"><br></div><div style class="gmail_default">That said, there are other options available that are probably less of a hassle for you:</div><div style class="gmail_default">
<br></div><div style class="gmail_default">1) Skip tkinter unless you _know_ you really need it. Do you plan on doing X-forwarding when you log in? Can you run the GUI app on your local machine before uploading the files you need for computation? Running GUIs locally rather than over the network is typically much faster, anyway.</div>
<div style class="gmail_default"><br></div><div style class="gmail_default">2) Submit a ticket to the supercomputer staff requesting that they install the software you need. There may be other 'gotchas' associated with installing certain software on supercomputers that the staff would know best.</div>
<div style class="gmail_default"><br></div><div style class="gmail_default">Good luck,<br>Jason</div></div></div></div>
</blockquote></div><br></div>