From: L. Michel Espinoza-Fonseca (mef_at_ddt.biochem.umn.edu)
Date: Fri Jan 26 2007 - 06:53:47 CST
Hi all,
My post is actually more a matter of curiosity. I'm compiling charm++
on a Blade machine (dual-core 2.6 GHz AMD Opteron processors). The
compilation started with no problem, but then it's been taking really
long time processing this:
make[2]: Leaving directory
`/home/bc1/espinoza/NAMD_2.6_Source/charm-5.9/mpi-linux-amd64/tmp'
touch basics
make QuickThreads/libqt.a
make[2]: Entering directory
`/home/bc1/espinoza/NAMD_2.6_Source/charm-5.9/mpi-linux-amd64/tmp'
make[2]: `QuickThreads/libqt.a' is up to date.
make[2]: Leaving directory
`/home/bc1/espinoza/NAMD_2.6_Source/charm-5.9/mpi-linux-amd64/tmp'
make converse-target
make[2]: Entering directory
`/home/bc1/espinoza/NAMD_2.6_Source/charm-5.9/mpi-linux-amd64/tmp'
../bin/charmc -c -I. conv-ccs.c
and then it doesn't move forward for long time (let's say, 1 hr) while
compiling conv-css.c. I've been wondering if that's OK (as long as I
don't have to wait for several hours). I've compiled charm++ on other
platforms, but right now I can't recall how much time it took me to
get it done. All your comments will be highly appreciated!
Thanks!
Michel
This archive was generated by hypermail 2.1.6 : Wed Feb 29 2012 - 15:44:19 CST