Juan, I finally got a spare moment to try and compile this stuff again.
When I run ./configure everything comes out okay. Then I try running the make, it wants to run the configure again...the trouble is, it keeps looping. When it finish the configure script, it starts it again, and it isn't doing any actual compiling. Did you have trouble with this? Austin -----Original Message----- From: Juan M. Courcoul [mailto:[EMAIL PROTECTED]] Sent: Friday, April 05, 2002 5:02 PM To: Matthew X. Economou Cc: [EMAIL PROTECTED] Subject: Re: Nessus 1.1.14 and MacOS 10.1.3 (aka Darwin 5.3) Thanks, Matthew. Following your advice, I now am a happy owner of a Nessus Security Scanner, version 1.1.14, running on MacOS 10.1.3. I'll probably be back later with questions, but first let me enjoy discovering Nessus' lastest goodies. Later, J. Courcoul Matthew X. Economou wrote: >>>>>>"Juan" == Juan M Courcoul <[EMAIL PROTECTED]> writes: >>>>>> > > Juan> I would like to get Nessus up and running in a Mac Powerbook > Juan> running MacOS X (10.1.3) but haven't been too successful. > > [problems linking nasl to _lrand48 and _srand48 elided] > > I have the same problem building NASL on MacOS X. According to the > lrand48 man page, one need only add the appropriate include > (stdlib.h), but when I compile a test program consisting only of a > call to lrand48, the compiler tells me it cannot resolve "_lrand48". > In fact, the "lrand48" and "_lrand48" symbols do not exist in any > libraries currently installed on my G3 system (including OpenSSL). > > What I did was to cut the relevant code from FreeBSD's libc (look > under libc/gens/ in CVS) and paste it into libnessus/rand.c. > > I don't grok autoconf, so I'll leave a permanent patch up to someone > with a clue. > > IMPORTANT NOTICE: This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you have received this message in error, you are hereby notified that we do not consent to any reading, dissemination, distribution or copying of this message. If you have received this communication in error, please notify the sender immediately and destroy the transmitted information.
