Ok, I had a memory overload and forgot something. I added the following lines to gdchart.h
#ifndef MAXFLOAT # define MAXFLOAT FLT_MAX #endif This is a replica of what the original programmer did with INT_MAX in gdchart.c. Also, in gdc.h, I changed GDC_NOVALUE from -MAXFLOAT to 0 (zero). ==================================================== Kent Wick, TxMHMR, Unix/Network Systems Programmer Email: [EMAIL PROTECTED] Phone: (512) 206-5931 Fax: (512) 206-4838 Snail mail: PO Box 12668, Austin, Tx 78711-2668 > -----Original Message----- > From: Jared Breland [SMTP:[EMAIL PROTECTED]] > Sent: Tuesday, Jul 23, 2002 3:36 PM > To: [EMAIL PROTECTED] > Subject: RE: compile error > > > hmm... On my system, I have /usr/include/float.h, which defines FLT_MAX, > and sets it to 3.4028234663852886e+38F. I've tried messing around with > the > gdchart.h to adjust for this (set MAXFLOAT = FLT_MAX, hardcode the value, > etc.), but haven't had any luck yet. Also, looking at the error message > again, I still think it has something to do with that out_graph function. > I don't know, though, I'm certainly not a developer. > > -- > Jared Breland > Information Security Intern > [EMAIL PROTECTED] > 901-748-5632 > > "Wick, Kent" > <[EMAIL PROTECTED] To: > [EMAIL PROTECTED] > ate.tx.us> cc: > Sent by: Subject: RE: compile > error > owner-nessus@list. > nessus.org > 07/23/2002 03:08 PM > > This is one of the other compile/portability errors that I ran into. > gdchart.h is looking for MAXFLOAT. Unfortunately, in AIX that > constant is in float.h which is not being included anywhere in the > current incarnation. Even if you do include that header file, you will > then run into the problem that the gdchart.h header file wants to > do a #define using a value of -MAXFLOAT (negative MAXFLOAT). > Unfortunately, in AIX this does not yield the same value as what > the gdchart programmer intended so you will have to take a guess > as to what he intended (possibly use MINFLOAT?). > ==================================================== > Kent Wick, TxMHMR, Unix/Network Systems Programmer > Email: [EMAIL PROTECTED] > Phone: (512) 206-5931 Fax: (512) 206-4838 > Snail mail: PO Box 12668, Austin, Tx 78711-2668 > > > -----Original Message----- > > From: Jared Breland [SMTP:[EMAIL PROTECTED]] > > Sent: Tuesday, Jul 23, 2002 2:52 PM > > To: [EMAIL PROTECTED] > > Subject: Re: compile error > > > > > > With the help of someone who e-mailed me off the list and pointed out > that > > the next_devpty function in ptycall.c was missing the closing brace, I > was > > able to get nessus-libraries to compile by simply adding the brace. > > Whoever maintains this, regardless of whether or not it's removed from > > nessus, would probably want to correct that. > > > > Unfortunately, I encountered another problem compiling nessus-core. I > > included the error snippet below. I checked out the out_graph function, > > and it doesn't appear to be defined anywhere.there's a call for it in > both > > html_graph_chart.c and as well as gdchart0.94b/gdchart.c, but the only > > mention of it anywhere else is the int GDC_out_graph in gdchart.h, which > > doesn't really seem to do anything to me. What do ya'll think? Any > > suggestions on how to fix this? Thanks allot. > > > > cd nessus && make > > gcc -g -O2 `sh ./cflags` -c html_graph_output.c > > In file included from html_graph_output.c:59: > > gdchart0.94b/gdchart.h:90: initializer element is not constant > > gdchart0.94b/gdchart.h:91: initializer element is not constant > > gdchart0.94b/gdchart.h:92: initializer element is not constant > > gdchart0.94b/gdchart.h:111: initializer element is not constant > > html_graph_output.c: In function `make_index': > > html_graph_output.c:1074: warning: implicit declaration of function > > `out_graph' > > make: 1254-004 The error code from the last command is 1. > > > > Stop. > > make: 1254-004 The error code from the last command is 2. > > > > Stop. > > > > -- > > Jared > > > > Pavel Kankovsky > > > > <[EMAIL PROTECTED] To:[EMAIL PROTECTED] > > f.cuni.cz> cc: > > > > Sent by: Subject: Re: compile > error > > [EMAIL PROTECTED] > > 07/23/2002 02:25 PM > > > > On 23 Jul 2002, Michel Arboi wrote: > > > > > IMHO, ptycall is a buggy & unportable piece of code that should be > > > replaced by popen() > > > > Does of the programs executed by ptyexecvp() (as far as I can tell, all > > wrapper plugins use it) need a terminal (or a pseudoterminal)? If the > > answer is no, you can get rid of ptycall.c. But I think it would be > better > > to use "manual" pipe()+fork()+exec*() instead of popen() because popen() > > (unlike ptyexecvp()) executes a shell and I do not think it would be a > > good idea to open the can of worms labelled "Shell Metacharacter". > > > > --Pavel Kankovsky aka Peak [ Boycott > Microsoft--http://www.vcnet.com/bms > > ] > > "Resistance is futile. Open your source code and prepare for > > assimilation." > > > > - > > [EMAIL PROTECTED]: general discussions about Nessus. > > * To unsubscribe, send a mail to [EMAIL PROTECTED] with > > "unsubscribe nessus" in the body. > > * To subscribe again, send a mail to [EMAIL PROTECTED] with > > "subscribe nessus" in the body > - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body. * To subscribe again, send a mail to [EMAIL PROTECTED] with "subscribe nessus" in the body
