guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Compilation and load-extension


From: Ludovic Courtès
Subject: Re: Compilation and load-extension
Date: Fri, 18 Dec 2009 11:33:06 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Hi,

Tristan Colgate <address@hidden> writes:

> Ah, sorry....
>
> ;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;;       or pass the --no-autocompile argument to disable.
> ;;; compiling /usr/local/share/guile/site/snmp/net-snmp.scm
> ;;; WARNING: compilation of
> /usr/local/share/guile/site/snmp/net-snmp.scm failed:
> ;;; key misc-error, throw args (#f "~A ~S" ("no code for module" (snmp
> net-snmp-primitive)) #f)
> STRING: Unknown (edit /etc/snmp/snmpd.conf)
> STRING: pinot
>
> the snmp net-snmp-primitive module is provided by a load-extension in
> the swig wrapper module.
> it's loaded by the module that swig has generated (snmp net-snmp)

So does the .so that’s loaded via ‘load-extension’ calls
‘scm_c_define_module ()’, right?  And ‘net-snmp.scm’ does:

  (define-module (snmp net-snmp)
    #:export (...))

  (load-extension ...)

  (use-modules (snmp net-snmp-primitive))

Right?

Could you make sure with strace(1) or some such that the right .so gets
loaded?

Thanks,
Ludo’.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]