#42156: libnasl: outdated and broken ---------------------+-------------------------------- Reporter: mojca@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libnasl ---------------------+-------------------------------- When checking the ticket #39383, it turns out that apart from #38114, `libnasl` is broken as well. I applied two naive patches (see attachments), but the software seems soooo awfully outdated. And given that there exists the `openvas-libnasl` port and that nobody reported a broken port, I strongly suspect that it could make a lot more sense to remove these `nessus` ports unless they are still needed (but they aren't usable anyway). I don't think that my libtool patch works properly anyway since even after applying it, the build fails with {{{ /bin/sh /path/to/work/libnasl/libtool --silent --mode=compile /usr/bin/clang -pipe -pipe -Os -arch x86_64 `sh ./cflags` -lrpcsvc `/opt/local/bin/nessus-config --libs` -o libnasl.la nasl_packet_forgery.lo nasl_socket.lo nasl_crypto.lo nasl_crypto2.lo nasl_http.lo nasl_host.lo nasl_text_utils.lo nasl_nessusd_glue.lo nasl_misc_funcs.lo nasl_cmd_exec.lo capture_packet.lo nasl_grammar.tab.lo nasl_tree.lo nasl_var.lo exec.lo lint.lo nasl_lex_ctxt.lo nasl_func.lo nasl_init.lo strutils.lo regex.lo lfind.lo preparse.lo nasl_server.lo nasl_debug.lo -rpath /opt/local/lib \ -version-info 4:9:2 libtool: compile: cannot determine name of library object from `libnasl.la' }}} What do you think about removing these ports? -- Ticket URL: <https://trac.macports.org/ticket/42156> MacPorts <http://www.macports.org/> Ports system for OS X