Cc: cmake@cmake.org; Bill Hoffman
Subject: Re: [CMake] CMake still broken post-2.8.1
Argh, premature send syndrome: the hang is definitely because cc.rex is missing
arguments and thus invokes the actual, two-stage C compiler without a source
file.
-Original Message-
From: Brad King
On 1/25/2012 9:06 AM, Phil Smith wrote:
Just to be clear: that doesn't mean CMake is right -- it's not passing all
the arguments it should. How to move this forward?
IMO the change to CMake that exposed this was correct. The ARG1
has always been a literal string placed in command shells
We've also provided other approaches elsewhere in this thread to
avoid the problem altogether by setting up your toolchain file to
skip compiler id detection.
OK, I'm willing to do that, but I can't figure out how to do so.
It seems like:
SET(CMAKE_C_COMPILER regina.exe cc.rex dcc.exe)
On 1/25/2012 10:53 AM, Phil Smith wrote:
We've also provided other approaches elsewhere in this thread to
avoid the problem altogether by setting up your toolchain file to
skip compiler id detection.
OK, I'm willing to do that, but I can't figure out how to do so.
Actually the previous
On 1/25/2012 1:50 PM, Phil Smith wrote:
Ok, that *maybe* gets me further. CMakeDetermineASM_DIGNUSCompiler.cmake (in
Modules\) is:
SET(ASM_DIALECT _DIGNUS)
SET(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT asmit.bat)
INCLUDE(CMakeDetermineASMCompiler)
SET(ASM_DIALECT)
and that gets invoked several
On Wednesday 25 January 2012, Brad King wrote:
On 1/25/2012 1:50 PM, Phil Smith wrote:
Ok, that *maybe* gets me further. CMakeDetermineASM_DIGNUSCompiler.cmake
(in Modules\) is:
SET(ASM_DIALECT _DIGNUS)
SET(CMAKE_ASM${ASM_DIALECT}_COMPILER_INIT asmit.bat)
: Wednesday, January 25, 2012 2:46 PM
To: cmake@cmake.org; Phil Smith
Subject: Re: [CMake] CMake still broken post-2.8.1
On Wednesday 25 January 2012, Brad King wrote:
On 1/25/2012 1:50 PM, Phil Smith wrote:
Ok, that *maybe* gets me further. CMakeDetermineASM_DIGNUSCompiler.cmake
(in Modules
On Wednesday 25 January 2012, Phil Smith wrote:
No, there's no What version are you? flag for dasm.
I added
set(CMAKE_ASM_DIGNUS_COMPILER_ID DIGNUS)
and now it seems to be invoking regina.exe with just the -o flag. Is that
the right SET ?
Looks good, are you sure this is still from
Smith
Sent: Friday, January 20, 2012 4:37 PM
To: 'Brad King'
Cc: Bill Hoffman; cmake@cmake.org
Subject: RE: [CMake] CMake still broken post-2.8.1
I'm confused because neither of your examples has the semicolon, but what we
need is:
regina.exe cc.rex dcc.exe CMakeCCompilerId.c
But it sounds like
On 1/21/2012 12:24 PM, Phil Smith wrote:
GOOD
C:/Program Files/Regina/regina.exe cc.rex dcc.exe CMakeCCompilerId.c
-- arg=[C:/Program Files/Regina/regina.exe]
-- arg=[cc.rex dcc.exe]
-- arg=[CMakeCCompilerId.c]
[snip]
BAD
c:/Program Files/Regina/regina.exe cc.rex;dcc.exe
Hoffman; cmake@cmake.org
Subject: Re: [CMake] CMake still broken post-2.8.1
On 1/21/2012 12:24 PM, Phil Smith wrote:
GOOD
C:/Program Files/Regina/regina.exe cc.rex dcc.exe CMakeCCompilerId.c
-- arg=[C:/Program Files/Regina/regina.exe]
-- arg=[cc.rex dcc.exe]
-- arg=[CMakeCCompilerId.c]
[snip
Cc: Bill Hoffman; cmake@cmake.org
Subject: Re: [CMake] CMake still broken post-2.8.1
On 1/21/2012 12:24 PM, Phil Smith wrote:
GOOD
C:/Program Files/Regina/regina.exe cc.rex dcc.exe CMakeCCompilerId.c
-- arg=[C:/Program Files/Regina/regina.exe]
-- arg=[cc.rex dcc.exe]
-- arg
] CMake still broken post-2.8.1
I'm back to this. I never got (or never understood!) an answer to this part of
the thread, which is where the breakage occurred:
--
If I comment out line 29 in CMakeDetermineCompilerId.cmake, it works with my
old toolchain file, but fails later with the new one
On 1/3/2012 1:29 PM, Phil Smith wrote:
If I comment out line 29 in CMakeDetermineCompilerId.cmake, it works with my
old toolchain file
[snip]
So -- why are semicolons being inserted?
The change was discussed here:
http://www.cmake.org/pipermail/cmake/2010-March/035810.html
: Re: [CMake] CMake still broken post-2.8.1
On 1/3/2012 1:29 PM, Phil Smith wrote:
If I comment out line 29 in CMakeDetermineCompilerId.cmake, it works with my
old toolchain file
[snip]
So -- why are semicolons being inserted?
The change was discussed here:
http://www.cmake.org/pipermail
On October 24, 2011 6:08 PM Bill Hoffman wrote:
So, right at the end it is doing this:
C:/Program Files (x86)/CMake
2.8/share/cmake-2.8/Modules/CMakeDetermineCompilerId.cmake(96):
EXECUTE_PROCESS(COMMAND ${CMAKE_${lang}_COMPILER}
${CMAKE_${lang}_COMPILER_ID_ARG1}
, January 20, 2012 3:50 PM
To: Phil Smith
Cc: Bill Hoffman; cmake@cmake.org
Subject: Re: [CMake] CMake still broken post-2.8.1
On October 24, 2011 6:08 PM Bill Hoffman wrote:
So, right at the end it is doing this:
C:/Program Files (x86)/CMake
2.8/share/cmake-2.8/Modules
On 1/20/2012 4:37 PM, Phil Smith wrote:
I'm confused because neither of your examples has the semicolon,
I was asking which one you need, so neither option has semicolons.
but what we need is:
regina.exe cc.rex dcc.exe CMakeCCompilerId.c
Okay.
But it sounds like you're saying that
I'm back to this. I never got (or never understood!) an answer to this part of
the thread, which is where the breakage occurred:
--
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
2011/10/27 Phil Smith p...@voltage.com:
Ok, tried the CMakeLists change, no change.
The Dignus-related files are attached.
Thanks, nothing strange in there.
Sorry for the delay, but I'm entering a not so much spare time loop
moreover I should admit I do not have any more debugging idea
for
-Original Message-
From: Bill Hoffman [mailto:bill.hoff...@kitware.com]
Sent: Wednesday, October 26, 2011 12:43 PM
To: Phil Smith
Cc: a.neundorf-w...@gmx.net; cmake@cmake.org; David Cole; Janet Graff; Brad King
Subject: Re: [CMake] CMake still broken post-2.8.1
So, since this is a cross
, October 26, 2011 12:43 PM
To: Phil Smith
Cc: a.neundorf-w...@gmx.net; cmake@cmake.org; David Cole; Janet Graff; Brad
King
Subject: Re: [CMake] CMake still broken post-2.8.1
So, since this is a cross compile situation, there is really no need to
run the compiler id code. You should be able to put
On Thu, 27 Oct 2011 05:40:24 -0700, Phil Smith wrote:
Hmm. My zosport.cmake is now (comments/blank lines removed):
SET(CMAKE_SYSTEM_NAME IBM_ZOS)
SET(CMAKE_C_COMPILER_ID_RUN 1)
SET(CMAKE_C_PLATFORM_ID MyPlatform)
SET(CMAKE_C_COMPILER_ID MyCompiler)
SET(CMAKE_C_COMPILER regina)
!
-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Thursday, October 27, 2011 9:00 AM
To: Phil Smith
Cc: Bill Hoffman; Brad King; cmake@cmake.org; Janet Graff;
a.neundorf-w...@gmx.net
Subject: Re: [CMake] CMake still broken post-2.8.1
2011/10/27 Phil Smith p
Narrowing down the cc list, everybody should be subscribed to the list..
2011/10/27 Phil Smith p...@voltage.com:
Toolchain.
You lack some var definitions in your toolchain:
see
http://www.cmake.org/Wiki/CMake_Cross_Compiling#The_toolchain_file
# where is the target environment
broken post-2.8.1
Narrowing down the cc list, everybody should be subscribed to the list..
2011/10/27 Phil Smith p...@voltage.com:
Toolchain.
You lack some var definitions in your toolchain:
see
http://www.cmake.org/Wiki/CMake_Cross_Compiling#The_toolchain_file
# where is the target environment
SET
2011/10/27 Phil Smith p...@voltage.com:
Yeah, I know everyone thinks out-of-source builds are better, but we have
peculiar requirements related to packaging up the object decks and the like
that really make out-of-source builds unappealing. We've been doing this for
almost 4 years, so we're
Ok, tried the CMakeLists change, no change.
The Dignus-related files are attached.
Thanks.
-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Thursday, October 27, 2011 1:47 PM
To: Phil Smith
Cc: CMake ML
Subject: Re: [CMake] CMake still broken post-2.8.1
2011
So, since this is a cross compile situation, there is really no need to
run the compiler id code. You should be able to put the following into
your toolchain file and avoid the compiler id check code altogether:
SET(CMAKE_C_COMPILER_ID_RUN 1)
SET(CMAKE_C_PLATFORM_ID MyPlatform)
still broken post-2.8.1
So, since this is a cross compile situation, there is really no need to
run the compiler id code. You should be able to put the following into
your toolchain file and avoid the compiler id check code altogether:
SET(CMAKE_C_COMPILER_ID_RUN 1)
SET(CMAKE_C_PLATFORM_ID
is what I'd expect. But the semicolon is still the problem here...
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Bill Hoffman
Sent: Monday, October 24, 2011 6:08 PM
To: cmake@cmake.org
Subject: Re: [CMake] CMake still broken post-2.8.1
Sorry for previous unfinished e-mail.
2011/10/25 Phil Smith p...@voltage.com:
Ah, ok. With 2.8.1:
C:/Program Files/Regina/regina.exe cc.rex dcc.exe CMakeCCompilerId.c
With 2.8.6:
C:/Program Files/Regina/regina.exe cc.rex;dcc.exe CMakeCCompilerId.c
Note the semicolon; where'd it come
On 10/25/2011 5:00 AM, Eric Noulard wrote:
2011/10/25 Phil Smithp...@voltage.com:
# Specify the cross-compilers
SET(CMAKE_C_COMPILER regina.exe cc.rex dcc.exe)
SET(CMAKE_CXX_COMPILER regina.exe cc.rex dcxx.exe)
I think CMAKE_[C|CXX]_COMPILER vars are supposed to contain
a command not
-Original Message-
From: Brad King [mailto:brad.k...@kitware.com]
Sent: Tuesday, October 25, 2011 9:14 AM
To: Phil Smith
Cc: Eric Noulard; cmake@cmake.org; Bill Hoffman; David Cole
Subject: Re: [CMake] CMake still broken post-2.8.1
On 10/25/2011 5:00 AM, Eric Noulard wrote:
2011/10/25 Phil Smithp
Hi,
I want to link a .so file with a executable.
how do I do that?
Regards
David
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
On Tuesday 25 October 2011, David Boesner wrote:
Hi,
I want to link a .so file with a executable.
how do I do that?
Use target_link_libraries().
And maybe find_library() before, depending on where that library comes from.
Giving some more information and also using a suitable subject would
2011/10/25 Phil Smith p...@voltage.com:
OK, but it should then reject the extra parameters, since it used to work.
Difficult to warn about a usage you did not even dream of ?
Now that we know I agree there should be a warning
(if not a clean failure with explanation).
In any case, I've
later supposed to undo this?
-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Tuesday, October 25, 2011 12:40 PM
To: Phil Smith
Cc: Brad King; cmake@cmake.org; Bill Hoffman; David Cole; Janet Graff
Subject: Re: [CMake] CMake still broken post-2.8.1
2011/10/25 Phil
this?
-Original Message-
From: Eric Noulard [mailto:eric.noul...@gmail.com]
Sent: Tuesday, October 25, 2011 12:40 PM
To: Phil Smith
Cc: Brad King; cmake@cmake.org; Bill Hoffman; David Cole; Janet Graff
Subject: Re: [CMake] CMake still broken post-2.8.1
2011/10/25 Phil Smith p...@voltage.com
No, alas. Code is proprietary and the compiler is licensed too.
From: David Cole [mailto:david.c...@kitware.com]
Sent: Tuesday, October 25, 2011 1:41 PM
To: Phil Smith
Cc: Eric Noulard; Brad King; cmake@cmake.org; Bill Hoffman; Janet Graff
Subject: Re: [CMake] CMake still broken post-2.8.1
On Tuesday 25 October 2011, Phil Smith wrote:
No, alas. Code is proprietary and the compiler is licensed too.
I think Phil asked here on the list like one year ago or so.
So, there are some things to be found in the archive.
Was this EBDIC stuff ?
Alex
--
Powered by www.kitware.com
Visit
: Tuesday, October 25, 2011 2:03 PM
To: cmake@cmake.org
Cc: Phil Smith; David Cole; Janet Graff; Brad King; Bill Hoffman
Subject: Re: [CMake] CMake still broken post-2.8.1
On Tuesday 25 October 2011, Phil Smith wrote:
No, alas. Code is proprietary and the compiler is licensed too.
I think Phil asked
A while ago, when 2.8.2 came out, I installed it and found that it hung
processing our CMakeLists.txt. There doesn't seem to be any debugging ability
in the code, so we went back to 2.8.1. Today I decided to try the latest
greatest (2.8.6): same result. This seems...bad.
It works fine with
Run cmake --trace and redirect the voluminous output to a file.
Inspect it for what's unusual and report back with that.
Or, if the file is not too large (I think 40k is our mailing list limit),
just send the whole thing along with a reply.
If it is really large, and you want us to look at it,
: David Cole [mailto:david.c...@kitware.com]
Sent: Monday, October 24, 2011 5:04 PM
To: Phil Smith
Cc: cmake@cmake.org
Subject: Re: [CMake] CMake still broken post-2.8.1
Run cmake --trace and redirect the voluminous output to a file.
Inspect it for what's unusual and report back
On 10/24/2011 5:42 PM, Phil Smith wrote:
Attached. ZTOOL is a wrapper for CMake, because we’re cross-compiling
with a two-stage compiler and have various other requirements.
We do a bunch of CMAKE –E commands before the cmake
-DCMAKE_TOOLCHAIN_FILE:string=%~dp0\zosport.cmake -GUnix Makefiles .\
: [CMake] CMake still broken post-2.8.1
On 10/24/2011 5:42 PM, Phil Smith wrote:
Attached. ZTOOL is a wrapper for CMake, because we're cross-compiling
with a two-stage compiler and have various other requirements.
We do a bunch of CMAKE -E commands before the cmake
47 matches
Mail list logo
