a source release tarball without having Flex (think of a source release
tarball being as much a platform-independent distribution format for
people *not* interested in development, and who are on platforms for
which there aren't binary packages, as a way of getting the source to do
development). Don't check Flex's capabilities in the configure script
(handling reentrant scanners would have to be done differently).
svn path=/trunk/; revision=22414
Configure options '--with-libgnutls-prefix' and '--with-libgcrypt-prefix' could
be used to indicate the path where the respective libraries had been installed.
However, these options could not be used to compile wireshark without the use
of them if installed on the system.
These two macros are not part of the wireshark project. configure.in has
therefore been modified so that wireshark can be compiled without gnutls or
gcrypt. Two configure options have been introduced : '--with-gnutls' and
'--with-gcrypt'. They take precedence on their 'prefix-specification'
counterpart or in other words, if '-with-gnutls=no' and
'--with-libgnutls-prefix' are used, wireshark will be compiled *without*
gnutls.
svn path=/trunk/; revision=22127
In all the places where a cast to "long long" or "unsigned long long"
was done, use G_GINT64_MODIFIER and get rid of the cast, as
1) there's no guarantee that "%ll" works
and
2) there's no guarantee that "long long" works
(the latter definitely does *NOT* work with MSVC++; the former doesn't
work with regular printf in MSVC++, but it might work with the GLib
printf-based functions).
svn path=/trunk/; revision=21978
what the complete set of warnings we should either try to fix or, for
cases where it can't be fixed, turn off or or avoid -Werror for. I'll
revert this change as soon as a complete set of buildbot builds start
with it.
svn path=/trunk/; revision=21917
"--disable-wireshark"; if they haven't explicitly said that they don't
want Wireshark, assume they do, and that they won't be happy if, when
the build finishes, they don't have Wireshark and weren't made
sufficiently aware that they wouldn't get it.
People who want to build TShark for machines that don't have GTK+
installed, but don't want to build Wireshark because they can't install
GTK+ on the build/target machine, can still do that; they just have to
explicitly specify "--disable-wireshark" to do it.
svn path=/trunk/; revision=21883
if the test for GTK+ fails; that lets the user insist on getting
Wireshark and gives them immediate feedback if they can't have it, so
they can either give up and just get TShark or fix the problem.
svn path=/trunk/; revision=21687
--enable-extra-gcc-checks set.
If we turn on -pedantic, try turning on -Wno-long-long as well, so that
it's not *so* pedantic that it rejects the 64-bit integral data types
that we explicitly require.
Constify a bunch of stuff, and make some other changes, to get rid of
warnings.
Clean up some indentation.
svn path=/trunk/; revision=21526
Add -Wpointer-arith to the GCC -W flags by default.
Make "extra-gcc-checks" and "warnings-as-errors" --enable flags rather
than --with flags - autoconf's model is that --enable is for turning
features on or off, --with is for enabling or disabling the use of
external packages (libpcap, Net-SNMP, GNU ADNS, etc.).
When testing whether the compiler is GCC, use the same style all the
time - check whether "x$GCC" equals "xyes". (The "x" might be overkill
- if you don't quote the arguments, it avoids a missing argument to
"test"/"[", but if you do, it might not be needed.)
svn path=/trunk/; revision=21492
(Temporarily disable the warnings as errors default on Unix to get
to get the buildbots and people with gcc40 going again until those
additional warnings gcc40 generates can be fixed-I'm working on it
ASAP)
Patch for configure.in which disables by default the treatment of
warnings as errors.
It can be enabled with './configure --with-warnings-as-errors'.
The macro will test first if GCC is present. If it's the case,
HAVE_WARNINGS_AS_ERRORS is defined. All the USING_GCC have been replaced
by HAVE_WARNINGS_AS_ERRORS.
With this switch, people won't suffer from unexpected warnings when
downloading svn sources during the transition time ;)
svn path=/trunk/; revision=21153
directory and most of the plugins to match the same command
put in the Makefile.nmake files for Windows compliations. Fix
a few warnings when compiling under gcc 3.4.4 on FreeBSD. Create
new automake file variable called USING_GCC in configure.in and
wiretap/configure.in to acomplish the above -Werror addition.
svn path=/trunk/; revision=21127
used with shared libraries, to fix some error that shows up in some
cases; some Apple documentation recommends it for most shared libraries.
svn path=/trunk/; revision=20312
http://developer.apple.com/releasenotes/DeveloperTools/RN-dyld/index.html
says
The static linker ld(1) supports building dylibs as either
-multi_module or -single_module. Conceptually, a multi-module
dylib is like a group of smaller dylibs - one per source file.
The extra meta-data in a multi-module dylib allowed (pre-10.4)
dyld to delay binding and running initializers on the individual
modules. In Mac OS X 10.4 dyld ignores all multi-module
meta-data and completely binds and runs all initializers the
same as if it were built single-module. In general, building
dylibs -single_module is preferred. The one case where
multi-module is still useful is it allows internal functions of
a dylib to be interposable. For instance, libSystem.dylib is
built multi_module so that malloc() can be overridden and all
uses of malloc in libSystem (e.g. strdup) would be redirected
to use the overridden version.
and we don't need the interposability for our dylibs, and Andreas Fink
indicates that it's necessary for the packaged Wireshark builds he's
doing.
svn path=/trunk/; revision=20301
--with-pcap=/usr/local will, if there's only a static libpcap in
/usr/local/lib, link with that rather than the system's dynamic version.
Move the check for Cygwin that adds -no-undefined to LDFLAGS to the
section checking for linker flags to add.
svn path=/trunk/; revision=20241
distcheck failure. Move the nmake build targets for airpdcap from
epan/dissectors to epan. This will probably break the Windows build.
svn path=/trunk/; revision=20231
move the files until these changes are checked in). Add an AC_DEFINE
for airpdcap (which will be removed once the changes have settled).
Update the airpdcap code to compile on non-Windows systems. Fix up
comments and whitespace to conform more closely to the rest of the
code base. Verified to compile under Windows and OS X.
svn path=/trunk/; revision=20227
Fix for http://bugs.wireshark.org/bugzilla/attachment.cgi?id=419&action=view
cross compilation fails
With the following change: Use only AC_CANONICAL_TARGET
From the autoconf manual:
The user is encouraged to use either `AC_CANONICAL_BUILD', or
`AC_CANONICAL_HOST', or `AC_CANONICAL_TARGET', depending on the
needs. Using `AC_CANONICAL_TARGET' is enough to run the two other
macros.
svn path=/trunk/; revision=19753
Jaap Keuter