This question is primarily for Michael, though also potentially for Kyle 
(who's out of town this week), but I wanted to get it onto the archives 
for future reference:

In trying to compile RE2 for use with the PGI compilers, I'm running into 
problems:

* The first is that if one's target compiler suite is set to 'pgi', RE2
   is still compiled with g++ (in part due to not querying the target
   compiler in the Makefiles; in part due to not forwarding the compiler
   choices on to the re2 makefile line), resulting in .o files that are not
   compatiable with pgCC due to different name-mangling schemes.

* If I fix those things and compile re2 with pgCC, I get a problem because
   the re2 Makefiles seem to hardcode in gcc flags like -Wno-sign-compare
   which pgi doesn't support.

* If I override the Makefile FLAGS macros that set -Wno-sign-compare, then
   I get pgi complaining that headers like tr1/unordered_set are not
   available.


All of this makes me think that getting re2 compiling with non-gcc 
compilers (and more to the point, non-g++ name-mangling-compatible 
compilers) may be a lost cause, but I wanted to make sure I wasn't missing 
anything obvious before giving up.

(It occurs to me that a workaround *might* be to force the compilation of 
re2-inferface.cc to always use g++ but that feels a little... icky to my 
tastes.  Although for that matter, so does most of the 
third-party/re2/Makefile).

Thanks,
-Brad

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers

Reply via email to