Nmap Development mailing list archives

Re: Error building nmap on amd64


From: Sven Klemm <sven () c3d2 de>
Date: Tue, 26 Aug 2008 07:21:23 +0200

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David,

David Fifield wrote:

| After thinking about this some more and discussing it with Fyodor, I
| have this proposal: remove support for shared modules from NSE.
|
| Currently there is only one shared module, bit.so, and it's tiny. We
| used to have another one, pcre.so, but it was changed to be linked
| statically into the nmap executable when we ran into a similar problem
| last year:

I have two more modules in my branches. And there are probably more to
come. Whenever you need a feature in NSE that a C library provides you
can just write a wrapper and use the functionality without recompiling
nmap.

|       Libtool, static libraries, and NSE modules
|       http://seclists.org/nmap-dev/2007/q4/0085.html
|
| The base problem is that statically linking the nmap executable and
| having dyamically loaded NSE modules are incompatible. We could work
| around it by using -fPIC and linking each module separately with liblua,
| but the Lua wiki insists that this approach "is *not* a good idea."
|
|       "Do Not Link Modules to the Lua Core Libraries"
|       http://lua-users.org/wiki/BuildingModules
|
| This change change would remove support for shared NSE modules and
| change bit into a statically linked module like bin, hash, and pcre.
| This is a moderately substantial change so please speak up if you have a
| reason why shared modules should be retained.

But this will stop common lua modules from working with NSE and it
will increase the effort needed to write lua bindings for NSE.

Cheers,
Sven

- --
Sven Klemm
http://cthulhu.c3d2.de/~sven/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkizktMACgkQevlgTHEIT4ZshgCfdeWgAGaR9WHkwBUMganYoBoV
iWwAn25RvxwbEH5+5aAHiNp+YyT48E7I
=KbpY
-----END PGP SIGNATURE-----

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


Current thread: