nessus and AMD64 again

"Gene C." <[email protected]>
Newsgroups gmane.comp.security.nessus.devel
Message-ID <[email protected]>
In my attempts to get nessus running (at least building for now) as a 64 bit 
application, I have hit a problem.

1.  First of all, there is a bug in gcc -O2 which causes a loop in gcc when 
building nessus-libraries ... this is described in 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=112678 and fixed by the 
associated patch.

2. I am use rpm as part of the build/install/etc. process but that is not 
relevent.

3.  The problem is that the libpcap libraries are installed into /usr/lib 
rather than /usr/lib64.  Per convention, /usr/lib is reserved for 32 bit 
libraries on dual (32/64 bit systems) and 64 bit libraries are placed in 
/usr/lib64.  The other libraries involved in nessus-libraries are properly 
installed into /usr/lib64.

4.  Is there some reason that nessus needs its own version of libpcap?  Are 
there some unique modifications that have been made to libpcap that are not 
part of libpcap 0.7.2?  Couldn't nessus simply use the regular libpcap and, 
at least on linux (or specifically Red Hat/Fedora) systems, not install its 
unique libpcap?

5. I have started looking for a fix but do not have one yet.  In any case, the 
files nessus-libraries/Makefile, nessus-libraries/libpcap-nessus/Makefile.in, 
and nessus-libraries/libpcap-nessus/Makefile need to be changed so that they 
do the right thing.

6. After a "quick look", it appears that the references to 
"${exec_prefix}/lib" in Makefile.in need to be changed to "${libdir}".  The 
is also a reference in the top level Makefile to "${prefix}/lib" rather than 
"${libdir}".  This last thing seems (to me) to be superfluous and you should 
let the lower level Makefile just do the work (like you do for libnessus).
-- 
Gene

_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.