complie error

[JINMEI Tatuya / 神明達哉]

At Mon, 25 Feb 2013 12:18:57 -0400,
Chris Taylor <Chris.Taylor at corp.eastlink.ca> wrote:

> > I had tried boost 1.53 but dropped back to version 1.52 and than
> > 1.50 but the last two still had the same compile error.

> diff --git a/tests/tools/Makefile.am b/tests/tools/Makefile.am index b4c1394..56cade3 100644
> --- a/tests/tools/Makefile.am
> +++ b/tests/tools/Makefile.am
> @@ -2,4 +2,4 @@
>  # portable (at least not exist on our Solaris buildbot).  For a short term  # workaround we stop building it until it's resolved.
>  #SUBDIRS = badpacket perfdhcp
> -SUBDIRS = badpacket perfdhcp
> +SUBDIRS = badpacket
> 
> I did apply the patch successfully 
> 
> 
> bash-3.2# patch -p0 < bind-10-patch
> patching file tests/tools/Makefile.am
> Hunk #1 succeeded at 3 with fuzz 2 (offset 1 line).
> 
> 
> 
> But when I run make again I get the following error, again, I am pretty sure I got the patch applied correctly.

Ah, in the case of release tar ball you may have to update
Makefile.in by hand, then rebuild everything from "make distclean".
Find the following line in bind10-1.0.0/tests/tools/Makefile.in

SUBDIRS = badpacket perfdhcp

and change it to

SUBDIRS = badpacket

> Below are the versions of gcc and g++ I am running
> 
> libgcc-4.1.2-54.el5
> gcc-4.1.2-54.el5
> gcc-c++-4.1.2-54.el5
> libgcc-4.1.2-54.el5

gcc/g++ 4.1.2 looks very old.  That's probably the reason for your
problem.  I don't remember whether we ever tried that version of gcc;
we know 4.2.x generally works okay.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.