nmap @7.01_0 build failure on Leopard/ppc

[khepler]

Build fails on Mac OS X 10.5.8/ppc with:

/usr/bin/g++-4.2 -c -I./liblinear -I./liblua -I./libdnet-stripped/include -I/opt/local/include -I/opt/local/include -I/opt/local/include -I./nbase -I./nsock/include -DHAVE_CONFIG_H -DNMAP_NAME=\"Nmap\" -DNMAP_URL=\"https://nmap.org\" -DNMAP_PLATFORM=\"powerpc-apple-darwin9.8.0\" -DNMAPDATADIR=\"/opt/local/share/nmap\" -D_FORTIFY_SOURCE=2 -no-cpp-precomp -pipe -Os -arch ppc -Wall -fno-strict-aliasing   nmap_dns.cc -o nmap_dns.o
nmap_dns.cc: In static member function ‘static bool DNS::Factory::ipToPtr(const sockaddr_storage&, std::string&)’:
nmap_dns.cc:1320: error: no match for ‘operator!=’ in ‘c != std::basic_string<_CharT, _Traits, _Alloc>::rend() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]()’
nmap_dns.cc: In static member function ‘static bool DNS::Factory::ptrToIp(const std::string&, sockaddr_storage&)’:
nmap_dns.cc:1385: error: no match for ‘operator!=’ in ‘it != std::basic_string<_CharT, _Traits, _Alloc>::rend() [with _CharT = char, _Traits = std::char_traits<char>, _Alloc = std::allocator<char>]()’
make: *** [nmap_dns.o] Error 1
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_nmap/nmap/work/nmap-7.01'
Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_nmap/nmap/work/nmap-7.01" && /usr/bin/make -w all 
Exit code: 2
Error: org.macports.build for port nmap returned: command execution failed

[khepler]

Sorry, the haspatch keyword is not applicable to this ticket; was confusion from editing multiple tickets simultaneously. Please remove.

[danielluke (Daniel J. Luke)]

10.5 isn't supported anymore - and I don't have access to a 10.5/ppc machine to try to fix this.

I'm guessing it would build with a newer compiler (ie macports clang), but I can't be sure.

If you (or someone with a 10.5/ppc machine) figures out a fix and uploads a patch, I'd be happy to include it.

Otherwise, I'm going to close this ticket (feel free to re-open with a patch that fixes it).