Hi Mike, I started the build on Nevada build 71. I shall be upgrading it to build 74 in a couple of days.
However, on build 71 I am seeing the following errors: 1) file arp-ioctl.c in /usr/src/cmd/nmap/nmap-4.20/libdnet-stripped/src does not compile due to following error: The following command caused the error: arp-ioctl.c:402: error: storage size of 'rnode' isn't known arp-ioctl.c:403: error: storage size of 'rt' isn't known arp-ioctl.c:411: error: `RNF_ROOT' undeclared (first use in this function) arp-ioctl.c:411: error: (Each undeclared identifier is reported only once arp-ioctl.c:411: error: for each function it appears in.) arp-ioctl.c:417: error: structure has no member named `at_hwaddr' arp-ioctl.c:439: error: storage size of 'ifarp' isn't known arp-ioctl.c:455: error: structure has no member named `if_arp_cache_head' arp-ioctl.c:456: error: structure has no member named `if_arp_cache_head' 2) /usr/src//cmd/quagga/quagga-0.99.8/zebra/rtread_sysctl.c fails to compile with following error: ../../quagga-0.99.8/zebra/rtread_sysctl.c", line 43: undefined symbol: CTL_NET "../../quagga-0.99.8/zebra/rtread_sysctl.c", line 47: undefined symbol: NET_RT_DUMP "../../quagga-0.99.8/zebra/rtread_sysctl.c", line 52: warning: implicit function declaration: sysctl (E_NO_IMPLICIT_DECL_ALLOWED) cc: acomp failed for ../../quagga-0.99.8/zebra/rtread_sysctl.c Regards, Ritu Mike Sullivan wrote: > Ritu Kamboj wrote: > >> I am building this on Solaris 10 Update 4 . Hence I had to manually >> install autoconf tool . I understand that these tools exist under >> /usr/sfw/bin on Nevada. > > > aha - you cannot build nevada bits on S10, so you're on your own there. > Or at least, you can _try_, but it may not work, and you'll have to > get help from someone other than me since I (and sfwnv) are nevada > based. > > The build instructions do point out the nevada requirement. > >> >> Thanks for the pointer about libcurl ...I shall add the idn package. > > > actually you probably shouldn't as it was built on nevada and may or > may not work on an older release. You may be able to build libidn > and the package on s10 and then install it, but it may need other > things s10 doesn't have. Again you're on your own. > > Mike
