charm AT lists.cs.illinois.edu

Subject: Charm++ parallel programming system

List archive

[charm] Build with --destination

From: Nels John Frazier <nfrazie1 AT uwyo.edu>
To: "charm AT cs.illinois.edu" <charm AT cs.illinois.edu>
Subject: [charm] Build with --destination
Date: Thu, 7 Jul 2016 19:23:47 +0000
Accept-language: en-US
Authentication-results: spf=none (sender IP is ) smtp.mailfrom=nfrazie1 AT uwyo.edu;
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99

Hi,

I'm working on building the latest release of Charm++ (6.7.1) and I would like to the installation to exist alongside a set of other tools and libraries.

For example, I have a directory /tools where I have sub directories where other software exists (/tools/bin, /tools/lib/, /tools/include, ect.) When I try to build/install charm++, I used the following command.

./build charm++ mpi-linux-x86_64 --basedir=/tools/ --destination=/tools/ --with-metis -j8

However, the make basics target has the following lines:

rm -rf ../lib ; mkdir ../lib

rm -rf ../lib_so ; mkdir ../lib_so; touch ../lib_so/.charmso

rm -rf ../examples

rm -rf ../tests

rm -rf ../doc ; ln -s ../doc ../doc

This ended up hosing my entire build environment (which included the metis dependency and broke the charm build.) This seems like an unreasonable behavior. Is there a way short of editing the makefile myself to allow charm to build into a directory without wiping out all other software in the same directory?

Thanks,

Nels Frazier

[charm] Build with --destination, Nels John Frazier, 07/07/2016