charm AT lists.siebelschool.illinois.edu

Subject: Charm++ parallel programming system

List archive

[charm] build passes -stdlib=libc++ on mac/gcc build and fails

From: Jozsef Bakosi <jbakosi AT lanl.gov>
To: charm <charm AT lists.cs.illinois.edu>
Subject: [charm] build passes -stdlib=libc++ on mac/gcc build and fails
Date: Tue, 8 May 2018 20:34:18 -0600
Authentication-results: illinois.edu; spf=pass smtp.mailfrom=jbakosi AT lanl.gov; dmarc=pass header.from=lanl.gov

Hi folks,

On mac, using the gnu compiler suite, the build passes the -stdlib=libc++
compiler argument during configure and thus fails, since g++ does not take
that
option. I tested this with 6e427c6ed, tag v6.8.2 is fine.

./build charm++ mpi-darwin-x86_64 --build-shared -j24 -g

$ less tmp/charmconfig.out
Error checking is enabled
AMPI error checking is enabled
Statistics collection is enabled
Charm tracing is enabled
Charm tracing communication thread is disabled
CharmDebug is enabled
Charm record/replay is enabled
CCS is enabled
Charm control point is enabled
Charm LB user data is disabled
Charm shrink expand is disabled
CharmPy support is disabled
Setting load balancing timer type as 'double'
### whether C++ compiler works
#include <stdio.h>
void foo(void) {
printf("Hello, world!\n");
}
mpicxx -dynamic -fPIC -fno-common -Wno-deprecated-declarations -stdlib=libc++
-mmacosx-version-min=10.7 -D_DARWIN_C_SOURCE -I../include -I. -c test.cpp -o
test.o
g++-mp-5: error: unrecognized command line option '-stdlib=libc++'

Please let me know if you need more info.

Thanks,
Jozsef

[charm] build passes -stdlib=libc++ on mac/gcc build and fails, Jozsef Bakosi, 05/08/2018
- RE: [charm] build passes -stdlib=libc++ on mac/gcc build and fails, White, Samuel T, 05/09/2018
  - Re: [charm] build passes -stdlib=libc++ on mac/gcc build and fails, Jozsef Bakosi, 05/09/2018