Hi, Thanks again for all the help! I finally gave up on 4.0.2 and downloaded the sources to 3.6.10 . I was able to get that to compile without too much difficulty :)
Best regards, -- Mun > -----Original Message----- > From: Mun Johl <mun.j...@wdc.com> > Sent: Wednesday, January 11, 2023 10:23 AM > To: Gerald Combs <ger...@wireshark.org>; Community support list for Wireshark > <wireshark-users@wireshark.org> > Subject: RE: [Wireshark-users] Issues compiling Wireshark on RHEL7 > > Hi, > > Thank you for the information and advice! I'll look into the rpm-setup.sh > script and maybe give it a go. But if I continue to have issues, > I'll downshift to Wireshark 3.6 as you have suggested. > > Regards, > > -- > Mun > > > rpm-setup.sh and the other -setup.sh scripts are documented in the > > Developer's Guide at > > > > https://www.wireshark.org/docs/wsdg_html_chunked/ChapterSetup.html#ChSetupUNIX > > > > We also use rpm-setup.sh to build the containers used in our CI jobs, which > > means that a vast robot army will complain if it doesn't > > work correctly. > > > > You'll probably have better luck building Wireshark 3.6 on RHEL7. That > > branch still has GitLab CI jobs that build and test using CentOS > > 7, but in the 4.0 branch we bumped a *lot* of required package versions and > > dropped the CentOS 7 jobs. > > > > On 1/11/23 8:48 AM, Mun Johl via Wireshark-users wrote: > > > Hi, > > > > > > I actually haven’t run rpm-setup.sh (uh-oh). I was working through the > > > instructions in the INSTALL file and didn’t realize I should > run > > rpm-setup.sh first. I think during my web searches I did find mention of > > that, but I was already knee deep and wasn’t sure if I should > > run it after I got started. > > > > > > Do you recommend I go ahead and run rpm-setup.sh now? That is, before I > > > try to manually install PCRE2? If that setup script will > > load all dependencies, that would be most excellent. > > > > > > Thank you and regards, > > > > > > -- > > > > > > Mun > > > > > > *From:* Wireshark-users <wireshark-users-boun...@wireshark.org> *On > > > Behalf Of *chuck c > > > *Sent:* Wednesday, January 11, 2023 6:37 AM > > > *To:* Community support list for Wireshark <wireshark-users@wireshark.org> > > > *Subject:* Re: [Wireshark-users] Issues compiling Wireshark on RHEL7 > > > > > > *CAUTION:**This email originated from outside of Western Digital. Do not > > > click on links or open attachments unless you recognize > > the sender and know that the content is safe.* > > > > > > Were there any errors when running tools/rpm-setup.sh? > > > > > > https://gitlab.com/wireshark/wireshark/-/blob/master/tools/rpm-setup.sh#L83 > > > <https://gitlab.com/wireshark/wireshark/- > > /blob/master/tools/rpm-setup.sh#L83> > > > > > > pcre2-devel \ > > > > > > On Tue, Jan 10, 2023 at 6:46 PM Mun Johl via Wireshark-users > > > <wireshark-users@wireshark.org <mailto:wireshark- > > us...@wireshark.org>> wrote: > > > > > > Hi, > > > > > > The error is just another missing library: > > > > > > CMake Error at > > > /usr/local/share/cmake-3.25/Modules/FindPackageHandleStandardArgs.cmake:230 > > > (message): > > > > > > Could NOT find PCRE2 (missing: PCRE2_LIBRARY PCRE2_INCLUDE_DIR) > > > (found > > > > > > version "") > > > > > > I didn’t want to mention it yet because I haven’t begun my search yet > > > for the lib or sources. Although, I appreciate your concern > > and inquisitiveness :) > > > > > > Best regards, > > > > > > -- > > > > > > Mun > > > > > > Can you share your error message? Anything like this: > > > > > > > > > https://ask.wireshark.org/question/29646/cmake-dependency-failed-for-v40-when-trying-to-build-an-rpm-package-from-a-source- > > tarball/ > > <https://ask.wireshark.org/question/29646/cmake-dependency-failed-for-v40-when-trying-to-build-an-rpm-package-from-a- > > source-tarball/> > > > > > > "but here I'm using CentOS 7.9 after changed the dependencies in > > > CMakeLists." > > > > > > Not sure what the CMakeList changes were. > > > > > > On Tue, Jan 10, 2023 at 6:14 PM Mun Johl via Wireshark-users > > > <wireshark-users@wireshark.org <mailto:wireshark- > > us...@wireshark.org>> wrote: > > > > > > Hi, > > > > > > Thank you for the link. I was able to get past the c-ares > > > issue—but unfortunately, another CMake Error awaits my attention. > > > > > > Best regards, > > > > > > -- > > > > > > Mun > > > > > > Suggestions for work-arounds: > > > > > > [Wireshark-dev] CARES to old for CentOS8? > > > > > > > > > https://www.wireshark.org/lists/wireshark-dev/202209/msg00017.html > > > <https://www.wireshark.org/lists/wireshark- > > dev/202209/msg00017.html> > > > > > > On Tue, Jan 10, 2023 at 3:55 PM Mun Johl via Wireshark-users > > > <wireshark-users@wireshark.org <mailto:wireshark- > > us...@wireshark.org>> wrote: > > > > > > Hi, > > > > > > I am attempting to compile Wireshark v4.0.2 on a RHEL7 server > > > and am running into problems. My current issue is that the > c- > > ares library is not installed on the server. I’ve downloaded the c-ares > > source code but it seems my compiler is too old to be able to > > compile c-ares. > > > > > > My questions are as follows: Is the “c-ares” library > > > *required* for the proper compilation of Wireshark? Are there any > > alternatives to using c-ares that I may be able to try? > > > > > > If c-ares is required, then I will try to install a newer > > > version of the compiler from sources--since our repos do not have > > anything newer. > > > > > > Thank you and regards, > > > > > > -- > > > > > > Mun > > > > > > > > > ___________________________________________________________________________ > > > Sent via: Wireshark-users mailing list > > > <wireshark-users@wireshark.org <mailto:wireshark-users@wireshark.org>> > > > Archives: https://www.wireshark.org/lists/wireshark-users > > > <https://www.wireshark.org/lists/wireshark-users> > > > Unsubscribe: > > > https://www.wireshark.org/mailman/options/wireshark-users > > <https://www.wireshark.org/mailman/options/wireshark-users> > > > mailto:wireshark-users-requ...@wireshark.org > > > <mailto:wireshark-users- > requ...@wireshark.org>?subject=unsubscribe > > > > > > > > > ___________________________________________________________________________ > > > Sent via: Wireshark-users mailing list > > > <wireshark-users@wireshark.org <mailto:wireshark-users@wireshark.org>> > > > Archives: https://www.wireshark.org/lists/wireshark-users > > > <https://www.wireshark.org/lists/wireshark-users> > > > Unsubscribe: > > > https://www.wireshark.org/mailman/options/wireshark-users > > <https://www.wireshark.org/mailman/options/wireshark-users> > > > mailto:wireshark-users-requ...@wireshark.org > > > <mailto:wireshark-users-requ...@wireshark.org>?subject=unsubscribe > > > > > > > > > ___________________________________________________________________________ > > > Sent via: Wireshark-users mailing list > > > <wireshark-users@wireshark.org <mailto:wireshark-users@wireshark.org>> > > > Archives: https://www.wireshark.org/lists/wireshark-users > > > <https://www.wireshark.org/lists/wireshark-users> > > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users > > <https://www.wireshark.org/mailman/options/wireshark-users> > > > mailto:wireshark-users-requ...@wireshark.org > > > <mailto:wireshark-users-requ...@wireshark.org>?subject=unsubscribe > > > > > > > > > ___________________________________________________________________________ > > > Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org> > > > Archives: https://www.wireshark.org/lists/wireshark-users > > > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users > > > > > > mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
