Wireshark mailing list archives
Re: Compilation issue on Mac OS
From: ajay saxena <aileronajay () gmail com>
Date: Fri, 21 Apr 2017 13:07:18 -0400
Hi Guy, The commits that you've referred to, 9e4c018e08d5a657f85f0cde0607db0a6d25ddf4 2c52d954d5713be1b809c3b668b0353d2b355c16 Are they present in the master branch on github? I cant seem to find them in the latest pull from github Ajays-MacBook-Pro:wireshark ajasaxen$ git show 9e4c018e08d5a657f85f0cde0607db0a6d25ddf4 fatal: bad object 9e4c018e08d5a657f85f0cde0607db0a6d25ddf4 Ajays-MacBook-Pro:wireshark ajasaxen$ git show 2c52d954d5713be1b809c3b668b0353d2b355c16 fatal: bad object 2c52d954d5713be1b809c3b668b0353d2b355c16 Also like you have stated, i do have the libraries in the non standard paths as I installed them using brew. But i did update the PKG_CONFIG_PATH so that the configure script was able to find these libraries. It was when i used make that the compilation failed. I believe I am having issues with the make as I dont have the commits mentioned above. On a side note is compiling with cmake not recommended due to some reason? Thanks, Ajay Thanks, Ajay On Fri, Apr 21, 2017 at 12:54 PM, Guy Harris <guy () alum mit edu> wrote:
On Apr 21, 2017, at 5:23 AM, ajay saxena <aileronajay () gmail com> wrote:Thanks for replying. I used cmake and it worked. I found out that i hadto 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. ____________________________________________________________ _______________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject= unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Compilation issue on Mac OS ajay saxena (Apr 20)
- Re: Compilation issue on Mac OS Alexis La Goutte (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS Guy Harris (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS Guy Harris (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS Guy Harris (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS Guy Harris (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS Guy Harris (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS Guy Harris (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS ajay saxena (Apr 21)
- Re: Compilation issue on Mac OS Alexis La Goutte (Apr 21)