Hello Brad,
On 30/07/14 15:32, Brad King wrote:
> Thanks. While reviewing the commits in 'next' again I realized
> that assuming paths are relative to CMAKE_BINARY_DIR may not be
> correct. Some projects may be nested inside others, and the
> CMAKE_BINARY_DIR may not be the proper location for a
I noticed the recent merge of liblzma broke the PGI compiler. The attached
patch should address the issues:
PGC-S-0037-Syntax error: Recovery attempted by deleting keyword static
(/home/chuck/Code/cmake/source/Utilities/cmliblzma/liblzma/check/sha256.c:
84)
Once that's fixed, then the 32-bit bui
It should be noted that the patch is really a set of workaround for PGI
compiler being broken and less to do with the code itself. If desired, I
could refactor the #if C99 test to use a CHECK_SOURCE_COMPILES at the
CMake level instead.
- Chuck
On Fri, Aug 1, 2014 at 2:22 PM, Chuck Atkins
wro
On 08/ 2/14 01:27 AM, Chuck Atkins wrote:
It should be noted that the patch is really a set of workaround for
PGI compiler being broken and less to do with the code itself. If
desired, I could refactor the #if C99 test to use a
CHECK_SOURCE_COMPILES at the CMake level instead.
I'm not intima
On Fri, Aug 1, 2014 at 2:43 PM, "C. Bergström"
wrote:
> I'm not intimately following this issue, but I can get you access to
> pathcc/pathCC to see if we work on this as well.
I've got an older ekopath 4.0.9 and 4.0.10 install that you gave us a while
back when I was setting up some LAPACK test
