Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-02 Thread Bill Somerville
On 01/12/2014 18:55, Brad King wrote: Hi Brad, thanks for the quick response on this one. On 12/01/2014 12:04 PM, Bill Somerville wrote: https://dl.dropboxusercontent.com/u/4192709/CMakeOutput.log.3.0.2 https://dl.dropboxusercontent.com/u/4192709/CMakeOutput.log.3.1.0-rc2 The relevant portion

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-02 Thread Brad King
On 12/02/2014 09:30 AM, Bill Somerville wrote: Ran with last nights snapshot dev binary build and it all seems to be fine now. Great, thanks for testing. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Bill Somerville
On 29/11/2014 12:02, Bill Somerville wrote: On 29/11/2014 11:58, Bill Somerville wrote: Hi, I have just tried 3.1.0-rc2 and my executable links are failing because all the link libraries are not being added. I use: add_executable (jt65code lib/jt65code.f90 wsjtx.rc) target_link_libraries

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Brad King
On 11/29/2014 06:58 AM, Bill Somerville wrote: -lgfortran -lquadmath -lm -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 but in 3.1.0-rc2 I get: -lquadmath -lm -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Bill Somerville
On 01/12/2014 16:33, Brad King wrote: Hi Brad, On 11/29/2014 06:58 AM, Bill Somerville wrote: -lgfortran -lquadmath -lm -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 but in 3.1.0-rc2 I get: -lquadmath -lm -lkernel32 -luser32 -lgdi32

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Bill Somerville
On 01/12/2014 17:04, Bill Somerville wrote: On 01/12/2014 16:33, Brad King wrote: Hi Brad, On 11/29/2014 06:58 AM, Bill Somerville wrote: -lgfortran -lquadmath -lm -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 but in 3.1.0-rc2 I get:

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Bill Somerville
On 01/12/2014 17:12, Bill Somerville wrote: On 01/12/2014 17:04, Bill Somerville wrote: On 01/12/2014 16:33, Brad King wrote: Hi Brad, On 11/29/2014 06:58 AM, Bill Somerville wrote: -lgfortran -lquadmath -lm -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Bill Somerville
I'm trying to debug this issue but the 3.1.0-rc2 use of linker response files is a PITA because they are created as temporary files and gone before I can look into them. Is there for flag I can set to stop them being used so I can see the whole link line? Regards Bill Somerville. --

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Brad King
On 12/01/2014 12:04 PM, Bill Somerville wrote: https://dl.dropboxusercontent.com/u/4192709/CMakeOutput.log.3.0.2 https://dl.dropboxusercontent.com/u/4192709/CMakeOutput.log.3.1.0-rc2 The relevant portion of these logs starts in the line Detecting Fortran compiler ABI info compiled with the

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Brad King
On 12/01/2014 01:37 PM, Bill Somerville wrote: I'm trying to debug this issue but the 3.1.0-rc2 use of linker response files is a PITA because they are created as temporary files and gone before I can look into them. Is there for flag I can set to stop them being used so I can see the

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-12-01 Thread Rolf Eike Beer
Brad King wrote: On 12/01/2014 12:04 PM, Bill Somerville wrote: One thing that looks suspicious are the lines mapping words to content along the lines of : arg [-lmingw32] == lib [mingw32] arg [-lgcc] == lib [gcc] arg [-lgcc_eh] == lib [gcc_eh] which in 3.1 look

[CMake] 3.1 can't link my MinGW executables any more.

2014-11-29 Thread Bill Somerville
Hi, I have just tried 3.1.0-rc2 and my executable links are failing because all the link libraries are not being added. I use: add_executable (jt65code lib/jt65code.f90 wsjtx.rc) target_link_libraries (jt65code wsjt) where wsjt is a static library target with Fortran and C functions. This

Re: [CMake] 3.1 can't link my MinGW executables any more.

2014-11-29 Thread Bill Somerville
On 29/11/2014 11:58, Bill Somerville wrote: Hi, I have just tried 3.1.0-rc2 and my executable links are failing because all the link libraries are not being added. I use: add_executable (jt65code lib/jt65code.f90 wsjtx.rc) target_link_libraries (jt65code wsjt) where wsjt is a static