Closed GoogleCodeExporter closed 9 years ago
This occurs when you have not installed the js [spidermonkey binary] although
jsunpack could be changed to say as much
Original comment by tebn...@gmail.com
on 28 Jan 2011 at 1:07
When I build using phython setup.py build it gives me the following error
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
build/temp.linux-x86_64-2.6/nidsmodule.o libnids-1.24/src/libnids.a
-L/usr/local/lib -L/opt/local/lib -lpcap -lnet -lglib-2.0 -lgthread-2.0 -o
build/lib.linux-x86_64-2.6/nidsmodule.so
gcc: libnids-1.24/src/libnids.a: No such file or directory
My os+machine(VM) --> Linux ubuntu 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21
17:40:44 UTC 2011 x86_64
GNU/Linux
Original comment by ali.tar...@gmail.com
on 28 Feb 2011 at 12:39
The error message now suggests that the user check that 'js' is in the path.
Original comment by urul...@gmail.com
on 26 May 2011 at 3:21
in regards to the "libnids-1.24/src/libnids.a: No such file or directory"
error, I suggest changing into the ./depends/pynids-0.6.1/libnids-1.24/src/
directory, type "make" then try the python setup.py build, and python setup.py
install again.
Original comment by urul...@gmail.com
on 26 May 2011 at 3:25
[deleted comment]
Adding on to the libnids compiling issue. Make sure you installed the glib
library.
Original comment by nicholas...@gmail.com
on 8 Sep 2011 at 4:10
same problem when building the pynids on ubuntu 10.04:
gcc: libnids-1.21/src/libnids.a: No such file or directory
follow suggestion to make in libnids-1.24/src/ but gives error:
killtcp.c:121:6: error: #elif with no expression
make[1]: *** [killtcp.o] Error 1
Original comment by tdr.lo...@gmail.com
on 27 Feb 2012 at 8:09
In case this helps, you need to run
configure
make
make install
from the libnids directory
Additionally, if you were building on a 64-bit Ubuntu system like BackTrack 5,
you may encounter "relocation R_X86_64_32 from .rodata" error. If so, set
environment variable CC to "gcc -fPIC" while running configure for libnids.
Original comment by cbchh...@gmail.com
on 17 Jul 2012 at 8:03
Original issue reported on code.google.com by
slarin...@gmail.com
on 30 Nov 2010 at 7:21