Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-08 Thread Jeff Morriss
On 01/05/14 14:40, Guy Harris wrote: On Jan 5, 2014, at 10:00 AM, Jeff Morriss jeff.morriss...@gmail.com wrote: On 01/04/2014 09:51 PM, Guy Harris wrote: On Jan 4, 2014, at 9:17 AM, Jeff Morriss jeff.morriss...@gmail.com wrote: 6) make # just to show that it works (I stopped the build

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-05 Thread Jeff Morriss
On 01/04/2014 09:51 PM, Guy Harris wrote: On Jan 4, 2014, at 9:17 AM, Jeff Morriss jeff.morriss...@gmail.com wrote: Ah, OK, I found a way to reproduce it (in current SVN): 1) rm -rf _cmake_build 2) mkdir _cmake_build cd _cmake_build 3) vi ../CMakeLists.txt 4) Move the -Wshorten-64-to-32

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-05 Thread Guy Harris
On Jan 5, 2014, at 10:00 AM, Jeff Morriss jeff.morriss...@gmail.com wrote: On 01/04/2014 09:51 PM, Guy Harris wrote: On Jan 4, 2014, at 9:17 AM, Jeff Morriss jeff.morriss...@gmail.com wrote: 6) make # just to show that it works (I stopped the build after a few C files were compiled)

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-04 Thread Jeff Morriss
On 01/03/2014 01:31 PM, Jeff Morriss wrote: On 01/02/2014 07:42 PM, Joerg Mayer wrote: On Thu, Jan 02, 2014 at 04:30:14PM -0800, Guy Harris wrote: Are we really encountering a case where the C compiler accepts -Wshorten-64-to-32 but the C++ compiler doesn't, or *vice versa*? Or are we

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-04 Thread Joerg Mayer
On Sat, Jan 04, 2014 at 12:17:35PM -0500, Jeff Morriss wrote: It's highly unlikely that this directory was previously used with a compiler that *did* support it (unless Fedora pushed out a compiler downgrade) but I suppose it is possible. I don't know. On my (32-bit) system, both compilers

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-04 Thread Jeff Morriss
On 01/04/2014 06:01 PM, Joerg Mayer wrote: On Sat, Jan 04, 2014 at 12:17:35PM -0500, Jeff Morriss wrote: It's highly unlikely that this directory was previously used with a compiler that *did* support it (unless Fedora pushed out a compiler downgrade) but I suppose it is possible. I don't

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-04 Thread Guy Harris
On Jan 4, 2014, at 9:17 AM, Jeff Morriss jeff.morriss...@gmail.com wrote: Ah, OK, I found a way to reproduce it (in current SVN): 1) rm -rf _cmake_build 2) mkdir _cmake_build cd _cmake_build 3) vi ../CMakeLists.txt 4) Move the -Wshorten-64-to-32 flag from where it is in the file to just

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-03 Thread Jeff Morriss
On 01/02/2014 07:42 PM, Joerg Mayer wrote: On Thu, Jan 02, 2014 at 04:30:14PM -0800, Guy Harris wrote: Are we really encountering a case where the C compiler accepts -Wshorten-64-to-32 but the C++ compiler doesn't, or *vice versa*? Or are we encountering a case where *neither* compiler

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Alexis La Goutte
Hi Jeff, I have also some time the some error message... With autotools, -Wshorten-64-to-32 is limited to only C... Regards, On Thu, Jan 2, 2014 at 10:02 PM, Jeff Morriss jeff.morriss...@gmail.comwrote: Hi folks, It took me a while to get my cmake build going again today; one of the

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Guy Harris
On Jan 2, 2014, at 1:34 PM, Alexis La Goutte alexis.lagou...@gmail.com wrote: I have also some time the some error message... With autotools, -Wshorten-64-to-32 is limited to only C... Because, to quote the comment in configure.ac: # The Qt headers generate a ton of shortening

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Jeff Morriss
On 01/02/14 16:34, Alexis La Goutte wrote: Hi Jeff, I have also some time the some error message... Only sometimes? I had to take that option out of CMakeLists.txt to get it compile. With autotools, -Wshorten-64-to-32 is limited to only C... True but my problem is with C compiler (it

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Guy Harris
On Jan 2, 2014, at 1:55 PM, Jeff Morriss jeff.morriss...@gmail.com wrote: On 01/02/14 16:34, Alexis La Goutte wrote: Hi Jeff, I have also some time the some error message... Only sometimes? I had to take that option out of CMakeLists.txt to get it compile. With autotools,

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Peter Wu
Hi, On Thursday 02 January 2014 16:02:08 Jeff Morriss wrote: It took me a while to get my cmake build going again today; one of the reasons was that the builds would immediately fail with: cc: error: unrecognized command line option -Wshorten-64-to-32 As far as I can tell the problem

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Jeff Morriss
On 01/02/14 17:05, Peter Wu wrote: Hi, On Thursday 02 January 2014 16:02:08 Jeff Morriss wrote: It took me a while to get my cmake build going again today; one of the reasons was that the builds would immediately fail with: cc: error: unrecognized command line option -Wshorten-64-to-32 As

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Jeff Morriss
On 01/02/14 17:15, Guy Harris wrote: On Jan 2, 2014, at 1:55 PM, Jeff Morriss jeff.morriss...@gmail.com wrote: On 01/02/14 16:34, Alexis La Goutte wrote: Hi Jeff, I have also some time the some error message... Only sometimes? I had to take that option out of CMakeLists.txt to get it

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Guy Harris
On Jan 2, 2014, at 2:44 PM, Jeff Morriss jeff.morriss...@gmail.com wrote: Cmake has that function which I listed that is supposed to do it for us but it doesn't seem to work (at least for me or at least not all the time). Given that at least two people have said that blowing away the build

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Joerg Mayer
On Thu, Jan 02, 2014 at 03:16:17PM -0800, Guy Harris wrote: On Jan 2, 2014, at 2:44 PM, Jeff Morriss jeff.morriss...@gmail.com wrote: Cmake has that function which I listed that is supposed to do it for us but it doesn't seem to work (at least for me or at least not all the time).

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Guy Harris
On Jan 2, 2014, at 4:21 PM, Joerg Mayer jma...@loplof.de wrote: On Thu, Jan 02, 2014 at 03:16:17PM -0800, Guy Harris wrote: But, if that's the case, was it cached when a compiler that *does* support -Wshorten-64-to-32 was used, and then a *different* compiler was used? (Building in a

Re: [Wireshark-dev] cmake giving options the compiler does not understand

2014-01-02 Thread Joerg Mayer
On Thu, Jan 02, 2014 at 04:30:14PM -0800, Guy Harris wrote: Are we really encountering a case where the C compiler accepts -Wshorten-64-to-32 but the C++ compiler doesn't, or *vice versa*? Or are we encountering a case where *neither* compiler accepts it, but CMake isn't detecting that? I