Re: nmap 4.03 compile error on mac os x 10.4.6

[Mark Boltz <mboltz () stonegizmo com>]

Hi,

I can reproduce the error on my MacBook Pro. I've also got the latest  
Tiger, only I'm on an Intel Mac, and using Xcode 2.2.1.

> The Xcode version is 2.0.
> Gcc -v output: gcc version 3.3 20030304 (Apple Computer, Inc. build  
> 1809)
> G++ -v output: gcc version 4.0.0 20041026 (Apple Computer, Inc.  
> build 4061)

I get

gcc -v
Using built-in specs.
Target: i686-apple-darwin8
Configured with: /private/var/tmp/gcc/gcc-5250.obj~12/src/configure -- 
disable-checking -enable-werror --prefix=/usr --mandir=/share/man -- 
enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg] 
[^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 -- 
build=powerpc-apple-darwin8 --with-arch=pentium-m --with- 
tune=prescott --program-prefix= --host=i686-apple-darwin8 -- 
target=i686-apple-darwin8
Thread model: posix
gcc version 4.0.1 (Apple Computer, Inc. build 5250)

and g++ matches.

Compiling 4.03 with

        ./configure --enable-shared=yes --enable-static=no

creates an error during make

g++ -Lnbase -Lnsock/src/  -o nmap main.o nmap.o targets.o tcpip.o  
nmap_error.o utils.o idle_scan.o osscan.o output.o scan_engine.o  
timing.o charpool.o services.o protocols.o nmap_rpc.o portlist.o  
NmapOps.o TargetGroup.o Target.o FingerPrintResults.o service_scan.o  
NmapOutputTable.o MACLookup.o nmap_tty.o nmap_dns.o  -lnbase -lnsock  
libpcre/libpcre.a -lpcap -lssl -lcrypto libdnet-stripped/src/.libs/ 
libdnet.a
i686-apple-darwin8-g++-4.0.1: libdnet-stripped/src/.libs/libdnet.a:  
No such file or directory
make: *** [nmap] Error 1

when compiling nmap.

Configuring with

        ./configure --enable-shared=no --enable-static=yes

compiles cleanly.

I *do* have GTK+ 2.8.16 installed for the sake of Ethereal.
I can provide the config.log files for anyone wanting to take a  
further look.

Compiling with just ./configure; make; make install works fine. I  
even got nmapfe this time since I did all the work to compile all the  
pieces to get Ethereal working first this time. :-)

So if you really want to have xnmap/nmapfe, I'd go for compiling the  
components of GTK+ first.

--
Mark Boltz






_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev