Wireshark-dev: Re: [Wireshark-dev] Compilation issue on Mac OS
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Fri, 21 Apr 2017 09:54:14 -0700
On Apr 21, 2017, at 5:23 AM, ajay saxena <aileronajay@xxxxxxxxx> wrote:

> Thanks for replying. I used cmake and it worked. I found out that i had to use cmake from a page on wiki.wireshark.com. I think it might be a good idea to include this information in README.macos file.

1) No, this is not a macOS issue.  It's an issue with installing libgcrypt or GeoIP's headers in a location that's not searched by default, e.g. in something under /opt rather than in /usr/local/include.  It would occur on *any* UN*X platform where those headers aren't in /usr/include or /usr/local/include or some other directory that the compiler searches by default.

2) The issue with gcrypt.h should be fixed by commit 9e4c018e08d5a657f85f0cde0607db0a6d25ddf4 and the issue with GeoIP.h should be fixed by commit 2c52d954d5713be1b809c3b668b0353d2b355c16, so there should be no need to use CMake to compile on macOS *even with headers not installed in /usr/local/include* (and, if not, that should be submitted as a bug, so we can fix it).

So, no, this does not belong in README.macos.