ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] RPM generation

From: Anders Broman <anders.broman@xxxxxxxxxxxx>
Date: Thu, 19 Apr 2018 17:59:18 +0000
Hi,
Logs included.
Regrads
Anders

-----Original Message-----
From: Wireshark-dev [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Peter Wu
Sent: den 19 april 2018 18:45
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Subject: Re: [Wireshark-dev] RPM generation

On Thu, Apr 19, 2018 at 03:12:33PM +0000, Anders Broman wrote:
> Hi,
> I’m struggling with my local build now which is a SVN checkout. I have managed to get the tarball built and the build continues from there but stops with:
> 
> -- Found Subversion: /usr/bin/svn (found version "1.8.19")
> -- Configuring incomplete, errors occurred!
> See also "/home/ericsson/build-one/packaging/rpm/BUILD/wireshark-2.9-ESVN-4119/build/CMakeFiles/CMakeOutput.log".
> See also "/home/ericsson/build-one/packaging/rpm/BUILD/wireshark-2.9-ESVN-4119/build/CMakeFiles/CMakeError.log".
> error: Bad exit status from /var/tmp/rpm-tmp.RQPfyB (%prep)
> 
> RPM build errors:
>     Bad exit status from /var/tmp/rpm-tmp.RQPfyB (%prep)
> CMakeFiles/rpm-package.dir/build.make:57: recipe for target 
> 'CMakeFiles/rpm-package' failed
> make[3]: *** [CMakeFiles/rpm-package] Error 1
> CMakeFiles/Makefile2:168: recipe for target 
> 'CMakeFiles/rpm-package.dir/all' failed
> make[2]: *** [CMakeFiles/rpm-package.dir/all] Error 2
> CMakeFiles/Makefile2:175: recipe for target 
> 'CMakeFiles/rpm-package.dir/rule' failed
> make[1]: *** [CMakeFiles/rpm-package.dir/rule] Error 2
> Makefile:201: recipe for target 'rpm-package' failed
> make: *** [rpm-package] Error 2
> 
> I don’t find anything obviously wrong in those log files, any tips what to look for?
> In the error log there is:
> cc: error: unrecognized command line option '-Wheader-guard'

CMake is testing this option (like any other), if it only shows up in the CMake logs, but not at compile time (make or ninja), it is harmless.

If it is not too large, can you provide the full cmake output?

Look for errors early in the process. For instance, without gcc-c++ installed on CentOS, I would get a very cryptic error down the road.
--
Kind regards,
Peter Wu
https://lekensteyn.nl
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

Attachment: CMakeError.log
Description: CMakeError.log

Attachment: CMakeOutput.log
Description: CMakeOutput.log