[Gilbert Ramirez <gram@xxxxxxxxxxxxxxx>]

"services" is a strange file; its Makefile dependency is just on the tool that creates it, but in reality it's a snapshot in time of data from a remote server.

There should be a way to run a build and NOT regenerated this 'services' files at all; the default services file that comes with the wireshark distro should suffice. When Gerald is rolling a new source release tarball, then the services file could be updated for the release.

A developer that WANTED to re-create services, could, but IMHO it shouldn't happen by default.

Gilbert

On Thu, Mar 1, 2012 at 7:02 AM, Martin Kaiser <lists@xxxxxxxxx> wrote:

Thus wrote Munish Dayal (munish.dayal@xxxxxxxxxxx):

> I am unable to compile wireshark-1.6.5 source code due to the following error.
> Build environment is Linux RHEL5. The compilation machine is not connected to the internet.

> Is there a way to bypass this step ?

> /usr/bin/perl ./tools/make-services.pl
> starting to fetch http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt ...
> request for http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt failed with result code:500 at ./tools/make-services.pl line 98.
> gmake[2]: *** [services] Error 9

I can't test this now, but could we just ignore the error from the make
target and continue anyway? IIRC this can be done (at least for gnu
make) by prefixing the rule with -

diff --git a/Makefile.am b/Makefile.am
index f79f5c4..ea3fa97 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -571,7 +571,7 @@ ps.c: print.ps $(srcdir)/tools/rdps.py
       $(PYTHON) $(srcdir)/tools/rdps.py $(srcdir)/print.ps ps.c

 services: tools/make-services.pl
-       $(PERL) $(srcdir)/tools/make-services.pl
+       -$(PERL) $(srcdir)/tools/make-services.pl

 CLEANFILES =           \
       *~              \

We'd need something similar for CMake and nmake, I don't know how that
works.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe