<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>No, alas. Code is proprietary and the compiler is licensed too.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> David Cole [mailto:david.cole@kitware.com] <br><b>Sent:</b> Tuesday, October 25, 2011 1:41 PM<br><b>To:</b> Phil Smith<br><b>Cc:</b> Eric Noulard; Brad King; cmake@cmake.org; Bill Hoffman; Janet Graff<br><b>Subject:</b> Re: [CMake] CMake still broken post-2.8.1<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Is your project's source publicly available? And are these compilers freely available, too?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It may be easier for us to help with a more complete picture of what's going on...<o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Tue, Oct 25, 2011 at 1:32 PM, Phil Smith <<a href="mailto:phil@voltage.com">phil@voltage.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Replying inline is getting unwieldy, so I've excerpted what I'm replying to here.<o:p></o:p></p><div><p class=MsoNormal><br>> Do you have a platform file for IBM_ZOS as well?<o:p></o:p></p></div><p class=MsoNormal>Yes, there's a platform file, IBM_ZOS.cmake:<br><br>INCLUDE(Platform/UnixPaths)<br><br>(exciting, huh?)<o:p></o:p></p><div><p class=MsoNormal><br>> what is the compiler ID found?<o:p></o:p></p></div><p class=MsoNormal>-- The C compiler identification is unknown<o:p></o:p></p><div><p class=MsoNormal><br>> may be you could try for force compiler:<o:p></o:p></p></div><p class=MsoNormal>I don't understand what that means. Well, maybe I partly do: it means skipping the compile-a-tiny-program. Since I don't understand why I care about that, I don't understand the rest. I inherited our use of CMake, hacked it into working three+ years ago, so maybe<o:p></o:p></p><div><p class=MsoNormal><br>>You did this in a clean build tree, right?<o:p></o:p></p></div><p class=MsoNormal>Well, I whacked the CMakeCache.txt and the CMakeFiles directory.<o:p></o:p></p><div><p class=MsoNormal><br>> May be with a REXX script ?<o:p></o:p></p></div><p class=MsoNormal>I don't think I can wrap it in a Rexx script -- that's how we got here, eh? I did try this:<br><br>SET(CMAKE_C_COMPILER "cc.rex")<br>SET(CMAKE_C_FLAGS "dcc.exe")<br><br>...since .rex is associated with Regina anyway. That got further, but it got to:<br>Check for working C compiler: C:/SVN/Dignus/cc.rex<br>...and that hung. It never called cc.rex in that case (I suspect this is why I was explicitly prefacing it with regina.exe -- it was a long time ago that I set this up!).<o:p></o:p></p><div><p class=MsoNormal><br>> Line 29 for which CMake version?<br>> Do you mean this line:<o:p></o:p></p></div><p class=MsoNormal>Yes, that's the line I meant.<o:p></o:p></p><div><p class=MsoNormal><br>> I think it means replace spaces with ";" in order to get a proper list.<o:p></o:p></p></div><p class=MsoNormal>OK, but why are arguments to the compiler supposed to be separated with semicolons? That doesn't seem right. Is something later supposed to undo this?<o:p></o:p></p><div><p class=MsoNormal><br>-----Original Message-----<br>From: Eric Noulard [mailto:<a href="mailto:eric.noulard@gmail.com">eric.noulard@gmail.com</a>]<br>Sent: Tuesday, October 25, 2011 12:40 PM<br>To: Phil Smith<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Cc: Brad King; <a href="mailto:cmake@cmake.org">cmake@cmake.org</a>; Bill Hoffman; David Cole; Janet Graff<br>Subject: Re: [CMake] CMake still broken post-2.8.1<o:p></o:p></p></div><div><div><p class=MsoNormal>2011/10/25 Phil Smith <<a href="mailto:phil@voltage.com">phil@voltage.com</a>>:<br>> OK, but it should then reject the extra parameters, since it used to work.<br><br>Difficult to warn about a usage you did not even dream of ?<br>Now that we know I agree there should be a warning<br>(if not a clean failure with explanation).<br><br>><br>> In any case, I've changed the toolchain file:<br>> ----------------------------------------<br>> # This is a CMake Toolchain file, required for cross-compiling using<br>> # the Dignus cross-compilers on Windows, compiling for z/OS.<br>><br>> # Tell CMAKE the target system name<br>> SET(CMAKE_SYSTEM_NAME "IBM_ZOS")<br><br>Do you have a platform file for IBM_ZOS as well?<br><br>if not<br>what is the compiler ID found?<br>"The C compiler identification is <WhatsInHere>"<br><br>may be you could try for force compiler:<br>see<br><a href="http://www.cmake.org/Wiki/CMake_Cross_Compiling#The_toolchain_file" target="_blank">http://www.cmake.org/Wiki/CMake_Cross_Compiling#The_toolchain_file</a><br>and<br>cmake --help-module CMakeForceCompiler<br><br>[...]<br><br>> ----------------------------------------<br>> ...and the behavior persists:<br>> C:/Program Files/Regina/regina.exe cc.rex;dcc.exe CMakeCCompilerId.c<br><br>You did this in a clean build tree, right?<br><br><br>> So it's not clear that that's a solution. I can't wrap the regina call because what will I wrap it in? BAT is criminally busted -- it eats equals signs. So later calls with -fwhatever=value will be broken.<br><br>May be with a REXX script ?<br>Just a wild guess because I did only write 2 lines of REXX in my life<br>so I may be wrong about the REXX capability.<br><br>> If I comment out line 29 in CMakeDetermineCompilerId.cmake, it works with my old toolchain file, but fails later with the new one, because it appears to call "the compiler" without the "flags", and regina with no arguments produces Help and exits.<br><br>Line 29 for which CMake version?<br>Do you mean this line:<br>STRING(REGEX REPLACE " +" ";" CMAKE_${lang}_COMPILER_ID_ARG1<br>"${CMAKE_${lang}_COMPILER_ID_ARG1}")<br><br><br>><br>> Why are the semicolons being inserted? If I wanted semicolons between the parameters, why wouldn't I just specify them?<br>><br>> Brad, your comment in the thread says:<br>>>Teach compiler identification to support values such as<br>>> export CC='gcc -g -O2'<br>>>by separating the arguments on spaces.<br>><br>> Not sure what "on spaces" means, but again, it seems wrong to me that anything is messing with my option format.<br><br>I think it means replace spaces with ";" in order to get a proper list.<br><br>May be the compiler args handling is broken in the cross-compiling case?<br>Such kind of setup?<br><br>--<br>Erk<br>Membre de l'April - « promouvoir et défendre le logiciel libre » -<br><a href="http://www.april.org" target="_blank">http://www.april.org</a><o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>