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] [PATCH] config.nice file for Wireshark

From: Stephen Fisher <stephentfisher@xxxxxxxxx>
Date: Tue, 8 May 2007 12:51:55 -0700
On Fri, Apr 20, 2007 at 09:47:46AM -0700, Mike Duigou wrote:

> Enclosed is a patch adapted from Apache APR via JXTA to create a 
> config.nice file for Wireshark. config.nice allows you to re-run 
> ./configure with the same options you used as the last time you ran 
> ./configure

How do you get it to pick up the previously used options?  Is it 
automatic?

> For unknown reasons I've lately had a lot of problems producing 
> working builds without rerunning autogen.sh and ./configure. I'm not 
> sure what has been changing or what's been wrong that prevents 
> rebuilding from working. Every couple of days for the last month or so 
> I find that I have to redo autogen.sh and ./configure or the build 
> will fail for various obscure reasons in seemingly random files. 'make 
> clean' is insufficient to repair the build environment but so far 
> re-running autogen.sh and ./configure does the job.

We had been messing around with the configure.in files a lot, including 
addding options to enable warnings as errors that was off by default, 
but now it's on.  Also adding additional warnings to the default build 
and the build when you ask for extra gcc flags.  Those changes may have 
contributed to your problem, sorry :)

> Rebuilding from scratch isn't too painful but the lack of a 
> config.nice means I have to remember what options and flags I used and 
> examining 'config.log' doesn't tell the complete story as it only has 
> the ./configure options and not the relevant CFLAGS, etc.
> 
> config.nice makes rerunning ./configure much simpler.

Saving the environment variables does sound like a good idea.  Anyone 
see a reason not to?


Steve