bind 9.2.4 build in 5.0a...

From: Ken Kleiner (ken_at_cs.uml.edu)
Date: 11/12/04

  • Next message: Gary Moody: "SUMMARY: Tru64 on a PWS500a" 
    Date: Fri, 12 Nov 2004 11:50:31 -0500
To: tru64-unix-managers@ornl.gov

    Hi...

       I'm trying to build bind 9.2.4 (from isc.org) on Tru64 5.0A and am
    getting the following errors, after running

    ./configure --disable-ipv6 AND running configure w./out the disable.

    Any ideas? Using the Compaq C compiler. Same problems with GCC.

       Thanks...

    -----

    making all in /cluster/members/member0/tmp/bind-9.2.4/make
    making all in /cluster/members/member0/tmp/bind-9.2.4/lib
    making all in /cluster/members/member0/tmp/bind-9.2.4/lib/isc
    making all in /cluster/members/member0/tmp/bind-9.2.4/lib/isc/include
    making all in
    /cluster/members/member0/tmp/bind-9.2.4/lib/isc/include/isc
    making all in /cluster/members/member0/tmp/bind-9.2.4/lib/isc/unix
    making all in
    /cluster/members/member0/tmp/bind-9.2.4/lib/isc/unix/include
    making all in
    /cluster/members/member0/tmp/bind-9.2.4/lib/isc/unix/include/isc
       cc -pthread -std -g -I/tmp/bind-9.2.4 -I./include
    -I./../pthreads/include -I../include -I./../include -I./..
    -D_REENTRANT -D_POSIX_PII_SOCKET -c socket.c
    cc: Error: socket.c, line 560: In this statement, "IPV6_PKTINFO" is not
    declared. (undeclared)
                         && cmsgp->cmsg_type == IPV6_PKTINFO) {
    -------------------------------------------^
    cc: Error: socket.c, line 700: In this statement, "IPV6_PKTINFO" is not
    declared. (undeclared)
                     cmsgp->cmsg_type = IPV6_PKTINFO;
    -----------------------------------^
    cc: Error: socket.c, line 1498: In this statement, "IPV6_PKTINFO" is
    not declared. (undeclared)
                         && (setsockopt(sock->fd, IPPROTO_IPV6, IPV6_PKTINFO,
    -----------------------------------------------------------^
    *** Exit 1
    Stop.
    *** Exit 1
    Stop.
    *** Exit 1
    Stop.
    *** Exit 1
    Stop.
             

    ----
<><  ><> <><  ><> <><  ><> <><  ><> <><  ><> <><
Ken Kleiner
System Manager
Computer Science Department
Umass Lowell
voice : 978 934 3645
fax : 978 934 3551
cell : 603 305 5800 (emergencies only, please)
ken@cs.uml.edu
  • Next message: Gary Moody: "SUMMARY: Tru64 on a PWS500a"

    Relevant Pages

    • Re: Thank You -- Thomas J. Gritzan
      ... realloc() and free. ... My compiler chokes without using the cast for mallocor calloc. ... exit(1); ...
      (comp.lang.c)
    • Re: brain teaser
      ... but Cobol standard does and that makes your code less portable. ... I'll use EXIT PARAGRAPH as soon as its available for my compiler. ... I do program with languages such as C# and Ruby (Ruby doesn't even ...
      (comp.lang.cobol)
    • Re: Is it always possible to write a COBOL program using only 1 sentence per paragraph?
      ... > available with your compiler. ... > to an EXIT PERFORM would do the conversion correctly. ... END-IF ... I'm supposed to accept COBOL ...
      (comp.lang.cobol)
    • Re: Cobol Myth Busters
      ... Both the HP compiler on my Alpha and the Fujitsu compiler ... What is the advantage of using EXIT PERFORM CYCLE over CONTINUE? ... If tests run too slowly,>10 seconds, lower repeat-factor to 10,000,000; ...
      (comp.lang.cobol)
    • Re: Gzip 1.3.12?
      ... exit status codes for either DCL, MMS, make or bash. ... the header files with exitand waitare #include. ... This is a sample of a wrapper: ... So, if you build the thing as below (with a recent compiler), what's ...
      (comp.os.vms)