Hello Hui --
You shouldn't have to do this. Actually, you shouldn't even have to
`make clean`. If you have a runtime built already, make a change to the
runtime sources, and then do `make` in $CHPL_HOME, your runtime should
get rebuilt as needed automatically. Are you changing any of the CHPL_*
configuration environment variables during this process?
greg
On Tue, 9 Feb 2016, Hui Zhang wrote:
I've figured out why. It seems you have to use 'make cleanall' or 'make
clobber' instead of just "make clean" inside runtime before you rebuild chapel
On Tue, Feb 9, 2016 at 9:55 PM, Hui Zhang <[email protected]> wrote:
Hello,
I made some changes in CHPL_HOME/runtime, then I
1. 'make clean' inside the runtime;
2. rm
-rfCHPL_HOME/lib/linux64.clang-included.arch-native.loc-flat.comm-none.tasks-fifo.tmr-gen
eric.mem-cstdlib.atomics-intrinsics.gmp-none.hwloc-none.re-none.wide-node16.fs-none
3. 'make' in CHPL_HOME.
I believe this used to work, but it doesn't this time, after rebuilding
chapel, it still uses old runtime library when I compile chapel programs.
Any ideas about how should I rebuild the runtime ? I'm using chapel 1.11,
CHPL_TASKS=fifo
thanks
--
Best regards
Hui Zhang
--
Best regards
Hui Zhang
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
