Re: SVN 11833 OSX 10.5.6 Compile Error

[Chris Clements <cclements () flatearth net>]

The fix worked like a charm.  Thanks for all the great work.


On Jan 23, 2009, at 5:09 PM, David Fifield wrote:

> On Fri, Jan 23, 2009 at 03:58:47PM -0700, David Fifield wrote:
> > On Fri, Jan 23, 2009 at 04:20:09PM -0600, Chris Clements wrote:
> > > Getting the following error while trying to compile:
> > >
> > > Compiling libnsock
> > > cd nsock/src && make
> > > ...
> > > gcc -c  -g -O2 -Wall  -I../../nbase  -DHAVE_CONFIG_H - 
> > > DNSOCK_VERSION=
> > > \"0.02\" -D_FORTIFY_SOURCE=2 -I../include -I../../libpcap  
> > > nsock_pcap.c
> > > -o nsock_pcap.o
> > > rm -f libnsock.a
> > > ar cr libnsock.a error.o filespace.o gh_list.o nsock_connect.o
> > > nsock_core.o nsock_iod.o nsock_read.o nsock_timers.o nsock_write.o
> > > nsock_ssl.o nsock_utils.o nsock_event.o nsock_pool.o netutils.o
> > > nsock_pcap.o
> > > rm -f libnsock.a
> > > ranlib: ar cr libnsock.a error.o filespace.o gh_list.o  
> > > nsock_connect.o
> > > nsock_core.o nsock_iod.o nsock_read.o nsock_timers.o nsock_write.o
> > > nsock_ssl.o nsock_utils.o nsock_event.o nsock_pool.o netutils.o
> > > nsock_pcap.o
> > > file: libnsock.a(nsock_utils.o) has no symbols
> > > ranlib: file: libnsock.a is not writable (No such file or directory)
> > > ar: internal ranlib command failed
> > > make[2]: *** [libnsock.a] Error 1
> > > make[1]: *** [../nsock/src/libnsock.a] Error 2
> > > make: *** [ncat_build] Error 2
> > > make: *** Waiting for unfinished jobs....
> > > ranlib: file: libnsock.a(nsock_utils.o) has no symbols
> > > ranlib libnsock.a
> > > ranlib: file: libnsock.a(nsock_utils.o) has no symbols
> >
> > It's a race condition in the build process, similar to the one  
> > fixed in
> > r9875. You can see that two different processes are trying to build
> > libnsock.a at the same time. I'll test a fix, but in the meantime you
> > should be able to use "make -j 1".
>
> Try r11836. The makefile target "all" depended on "nsock_build" and
> "ncat", which "ncat" depended on "nsock_build". That set up a  
> situation
> where two "nsock_build"s could be running simultaneously.
>
> David Fifield


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