Re: [Wireshark-dev] Mac Build Error

> On Jan 26, 2016, at 3:33 AM, Guy Harris wrote: > > On Jan 25, 2016, at 4:39 PM, David Morsberger wrote: > >> After a detailed analysis of cmake, I believe this is the solution and not >> just fixing the symptom. >> >> cmake uses /usr/bin/xcodebuild when using -G Xcode. The internal behavi

Re: [Wireshark-dev] Mac Build Error

On Jan 25, 2016, at 4:39 PM, David Morsberger wrote: > After a detailed analysis of cmake, I believe this is the solution and not > just fixing the symptom. > > cmake uses /usr/bin/xcodebuild when using -G Xcode. The internal behavior of > cmake is significantly different when using xcodebuil

Re: [Wireshark-dev] Mac Build Error

> On Jan 20, 2016, at 12:02 PM, Stig Bjørlykke wrote: > > On Wed, Jan 20, 2016 at 3:48 PM, David Morsberger > wrote: > My current workaround is the following change to CMakeLists.txt : > -if(NOT CMAKE_C_COMPILER_ID MATCHES "MSVC") > +if(NOT (CMAKE_C_COMPILER_ID MATCH

Re: [Wireshark-dev] Mac Build Error

On Fri, Jan 22, 2016 at 9:06 AM, Guy Harris wrote: > On Jan 21, 2016, at 11:42 PM, Roland Knall wrote: > > > Sorry to disappoint ;-), but it can be done, just not in a convenient > way. And the 9oo10 mostly is fixed by using a newer version then 2.8.12 for > CMake. There are some issues already

Re: [Wireshark-dev] Mac Build Error

On Jan 21, 2016, at 11:42 PM, Roland Knall wrote: > Sorry to disappoint ;-), but it can be done, just not in a convenient way. > And the 9oo10 mostly is fixed by using a newer version then 2.8.12 for CMake. > There are some issues already with the RC compiler and the NMake Generator > (does no

Re: [Wireshark-dev] Mac Build Error

On Fri, Jan 22, 2016 at 8:26 AM, Guy Harris wrote: > On Jan 21, 2016, at 9:36 PM, Roland Knall wrote: > > > FYI, the only sure-fire way in CMAKE to set specific only linker flags > is using the target properties. > > So what's the best way to, within a .cmake file, create a temporary > target, w

Re: [Wireshark-dev] Mac Build Error

On Jan 21, 2016, at 9:36 PM, Roland Knall wrote: > FYI, the only sure-fire way in CMAKE to set specific only linker flags is > using the target properties. So what's the best way to, within a .cmake file, create a temporary target, with those properties, and with a particular small piece of so

Re: [Wireshark-dev] Mac Build Error

On Fri, Jan 22, 2016 at 1:40 AM, Guy Harris wrote: > > > This means we can't use CMAKE_REQUIRED_FLAGS, and have to find some > *other* way to specify the flag to be tested. FYI, the only sure-fire way in CMAKE to set specific only linker flags is using the target properties. The following code m

Re: [Wireshark-dev] Mac Build Error

On Jan 21, 2016, at 2:53 PM, David Morsberger wrote: >> On Jan 21, 2016, at 3:28 PM, Guy Harris wrote: >> >>> On Jan 21, 2016, at 12:10 PM, David Morsberger wrote: >>> >>> I think this is a bug in cmake because: >>> >>> 1. the 'and run' in "CheckCSourceRuns: Check if the given C source code

Re: [Wireshark-dev] Mac Build Error

Sent from my iPhone > On Jan 21, 2016, at 3:28 PM, Guy Harris wrote: > >> On Jan 21, 2016, at 12:10 PM, David Morsberger wrote: >> >> I think this is a bug in cmake because: >> >> 1. the 'and run' in "CheckCSourceRuns: Check if the given C source code >> compiles and runs" should imply lin

Re: [Wireshark-dev] Mac Build Error

On Jan 21, 2016, at 12:10 PM, David Morsberger wrote: > I think this is a bug in cmake because: > > 1. the 'and run' in "CheckCSourceRuns: Check if the given C source code > compiles and runs" should imply linking and executing the software. Yes, and it *does* imply that. The problem is that

Re: [Wireshark-dev] Mac Build Error

On Thu, Jan 21, 2016 at 2:29 PM, Guy Harris wrote: > On Jan 21, 2016, at 6:08 AM, David Morsberger wrote: > > > It appears the linker isn’t called when the -c and the -o options are > present. > > Correct. It's not *supposed* to be called. In UNIX C compilers, the "-c" > flag means "compile to

Re: [Wireshark-dev] Mac Build Error

On Jan 21, 2016, at 6:08 AM, David Morsberger wrote: > It appears the linker isn’t called when the -c and the -o options are present. Correct. It's not *supposed* to be called. In UNIX C compilers, the "-c" flag means "compile to an object file, but don't link the resulting object file into

Re: [Wireshark-dev] Mac Build Error

I went down a rabbit hole and pulled myself back out. I narrowed it down to the following. We are using cmake to check if the linker supports ‘-Wl,—as-needed'. The test compile (and link?) command cmake builds using ‘cmake -G Xcode’ does not fail. The command from ‘cmake -G’ has been narrowed

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 3:22 PM, Guy Harris wrote: > On Jan 20, 2016, at 11:09 AM, David Morsberger > wrote: > > > This is what I am also tracking down. It has to do with the way cmake is > instantiating the compiler. The --serialized-diagnostics option is what > appears to be hiding the error.

Re: [Wireshark-dev] Mac Build Error

On Jan 20, 2016, at 11:09 AM, David Morsberger wrote: > This is what I am also tracking down. It has to do with the way cmake is > instantiating the compiler. The --serialized-diagnostics option is what > appears to be hiding the error. --serialize-diagnostics takes an argument, which is the n

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 1:26 PM, Guy Harris wrote: > On Jan 20, 2016, at 4:47 AM, David Morsberger wrote: > > > I am getting actual errors within Xcode after ‘cmake -G Xcode’. This can > easily be resolved by not testing ‘—as-needed’ or ‘—pie’ when XCODE just > like what is done for MSVC. > > Te

Re: [Wireshark-dev] Mac Build Error

On Jan 20, 2016, at 4:47 AM, David Morsberger wrote: > I am getting actual errors within Xcode after ‘cmake -G Xcode’. This can > easily be resolved by not testing ‘—as-needed’ or ‘—pie’ when XCODE just like > what is done for MSVC. Testing --as-needed should fail with the OS X linker whether

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 12:02 PM, Stig Bjørlykke wrote: > On Wed, Jan 20, 2016 at 3:48 PM, David Morsberger > wrote: > > My current workaround is the following change to CMakeLists.txt : >> >> -if(NOT CMAKE_C_COMPILER_ID MATCHES "MSVC") >> +if(NOT (CMAKE_C_COMPILER_ID MATCHES "MSVC" OR XCODE)) >

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 3:48 PM, David Morsberger wrote: > My current workaround is the following change to CMakeLists.txt : > > -if(NOT CMAKE_C_COMPILER_ID MATCHES "MSVC") > +if(NOT (CMAKE_C_COMPILER_ID MATCHES "MSVC" OR XCODE)) > set(WIRESHARK_LD_FLAGS > -Wl,--as-needed > >

Re: [Wireshark-dev] Mac Build Error

> On Jan 20, 2016, at 10:14 AM, Alexis La Goutte > wrote: > > > >> On Wed, Jan 20, 2016 at 3:48 PM, David Morsberger >> wrote: >> >> >>> On Wed, Jan 20, 2016 at 8:43 AM, Stig Bjørlykke wrote: On Wed, Jan 20, 2016 at 1:47 PM, David Morsberger wrote: I am getting ac

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 3:48 PM, David Morsberger wrote: > > > On Wed, Jan 20, 2016 at 8:43 AM, Stig Bjørlykke > wrote: > >> On Wed, Jan 20, 2016 at 1:47 PM, David Morsberger >> wrote: >> >> > I am getting actual errors within Xcode after ‘cmake -G Xcode’. This can >>> easily be resolved by not

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 8:43 AM, Stig Bjørlykke wrote: > On Wed, Jan 20, 2016 at 1:47 PM, David Morsberger > wrote: > > I am getting actual errors within Xcode after ‘cmake -G Xcode’. This can >> easily be resolved by not testing ‘—as-needed’ or ‘—pie’ when XCODE just >> like what is done for MS

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 1:47 PM, David Morsberger wrote: > I am getting actual errors within Xcode after ‘cmake -G Xcode’. This can > easily be resolved by not testing ‘—as-needed’ or ‘—pie’ when XCODE just > like what is done for MSVC. > Ah, yes, I forgot about this. I have tried to fix this e

Re: [Wireshark-dev] Mac Build Error

> On Jan 20, 2016, at 2:48 AM, Stig Bjørlykke wrote: > > On Wed, Jan 20, 2016 at 3:28 AM, David Morsberger > wrote: > I am trying to create support and possibly instructions for Xcode. > > The only issue I have with using Xcode is > https://bugs.wireshark.org/bugzi

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 20, 2016 at 3:28 AM, David Morsberger wrote: > I am trying to create support and possibly instructions for Xcode. > The only issue I have with using Xcode is https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11816 -- Stig Bjørlykke ___

Re: [Wireshark-dev] Mac Build Error

> On Jan 19, 2016, at 9:11 PM, Guy Harris wrote: > > On Jan 18, 2016, at 7:04 AM, David Morsberger wrote: > >> Not exactly sure how the outdated file showed up in the wireshark source >> (not build) hierarchy. My guess is it was due to a cmake run because of the >> following. >> 1. mkdir bui

Re: [Wireshark-dev] Mac Build Error

On Jan 18, 2016, at 7:04 AM, David Morsberger wrote: > Not exactly sure how the outdated file showed up in the wireshark source (not > build) hierarchy. My guess is it was due to a cmake run because of the > following. > 1. mkdir build > 2. cd build > 3. cmake .. to include cmake -G Xcode ..

Re: [Wireshark-dev] Mac Build Error

On 18-01-2016 15:04, David Morsberger wrote: On Jan 18, 2016, at 2:48 AM, Stig Bjørlykke mailto:s...@bjorlykke.org>> wrote: On Mon, Jan 18, 2016 at 6:27 AM, David Morsberger mailto:d...@morsberger.com>> wrote: I have been unable to resolve the following build errors on my Mac with 1

Re: [Wireshark-dev] Mac Build Error

On Mon, Jan 18, 2016 at 4:04 PM, David Morsberger wrote: > Not exactly sure how the outdated file showed up in the wireshark source > (not build) hierarchy. > Have a look at the timestamp for some of the other generated files to find when this happened. Maybe you did a build with this source dir

Re: [Wireshark-dev] Mac Build Error

> On Jan 18, 2016, at 2:48 AM, Stig Bjørlykke wrote: > > On Mon, Jan 18, 2016 at 6:27 AM, David Morsberger > wrote: > I have been unable to resolve the following build errors on my Mac with 10.11. > > Maybe you have a outdated declare_wslua.h in your source director

Re: [Wireshark-dev] Mac Build Error

On Mon, Jan 18, 2016 at 6:27 AM, David Morsberger wrote: > I have been unable to resolve the following build errors on my Mac with > 10.11. > Maybe you have a outdated declare_wslua.h in your source directory? Try deleting this. -- Stig Bjørlykke __

Re: [Wireshark-dev] Mac Build Error

I have been unable to resolve the following build errors on my Mac with 10.11. The perl code, the heavy use of macros, and lack of experience with lua was just a little too much. I did the ‘make maintainer-clean’, removed my build directory, re-ran ./autogen.sh, and re-ran the configure scrip

Re: [Wireshark-dev] Mac Build Error

On Wed, Jan 13, 2016 at 9:55 PM, Guy Harris wrote: > > On Jan 13, 2016, at 6:30 PM, David Morsberger wrote: > > > I am receiving the following error after I reset the HEAD to the latest. > > > > Mac OS 10.11 with Xcode > > > > Thoughts? > > Try doing "make maintainer-clean", re-run ./autogen.sh,

Re: [Wireshark-dev] Mac Build Error

On Jan 13, 2016, at 6:30 PM, David Morsberger wrote: > I am receiving the following error after I reset the HEAD to the latest. > > Mac OS 10.11 with Xcode > > Thoughts? Try doing "make maintainer-clean", re-run ./autogen.sh, re-run the configure script, and recompile; there might be some o

[Wireshark-dev] Mac Build Error

I am receiving the following error after I reset the HEAD to the latest. Mac OS 10.11 with Xcode Thoughts? /usr/bin/perl ../../../epan/wslua/make-taps.pl ../../../epan/wslua/taps taps_wslua.c taps.txt ../../../epan/wslua /Applications/Xcode.app/Contents/Developer/usr/bin/make all-am CC