[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-dev
Subject:    Re: [Wireshark-dev] Latest code broken?
From:       Guy Harris <guy () alum ! mit ! edu>
Date:       2015-03-17 6:39:43
Message-ID: 5DA89939-9294-46E6-8998-FCB6DE64CBDA () alum ! mit ! edu
[Download RAW message or body]


On Mar 16, 2015, at 11:14 PM, Anil <anilkumar911@gmail.com> wrote:

> compiling on a different machine, the problem does not show up. Wondering what \
> cleanup needs to be done on the old build machine. Are there any files other than \
> under the source tree, that needs to be cleaned up ?

If you built from a Git checkout, then:

	if you built with ./configure rather than CMake, I would do:

		make maintainer-clean
		./autogen.sh
		./configure
		make

	if you built with CMake, I would, from the directory in which the Wireshark source \
directory is contained:

		rm -rf build
		mkdir build
		cd build
		cmake ../{the name of the Wireshark source directory}
		make

If you built from a downloaded source tarball, I would:

	download the latest source tarball;

	do an rm -rf of the Wireshark source directory;

	extract from the source tarball;

	then:

		if you are building with ./configure rather than CMake:

			cd to the extracted source directory;
			./configure;
			make

		if you are building with CMake:

			mkdir build (if that fails with "File exists", do "rm -rf build" followed by \
"mkdir build");  cd build
			cmake ../{the name of the Wireshark source directory}
			make

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe


[prev in list] [next in list] [prev in thread] [next in thread]