<dsmith-work>pallagun: dynamically loaded .so's are looked up in the extendion(s) dir <pallagun>dsmith-work: oh! I recall hearing of strace once or twice, I'll see what that can tell me. Thanks <dsmith-work>pallagun: what does pkg-config --variable=extensiondir guile-2.0 say? <pallagun>dsmith-work: it says "/usr/lib64/guile/2.0/extensions" <pallagun>also: wow, strace says many, many things <dsmith-work>pallagun: Probably should not include the ".so" in your argument. <pallagun>access("/home/user/.ld_library_path/libguile-scg.so", R_OK) = 0 <pallagun>open("/home/user/.ld_library_path/libguile-scg.so", O_RDONLY|O_CLOEXEC) = 9 <pallagun>dsmith-work: those two line are the only ones referencing my .so file <pallagun>there are about 8 more lines before guile comes back and tells me "file not found" and none of them mention my .so file <pallagun>it does appear to check /usr/lib64 and /usr/lib64/guile/2.0/extensions for my .so file as well, where it fails to find it (since I didn't put it there) <dsmith-work>So is the name of your init function correct? ISTR something like when it can't get to that name, an error is returned, which eventually percolates up to "file not found". <pallagun>oh really? I can check on that, one moment <pallagun>I belive it's right. my scm looks like "(load-extension "libguile-scg" "init_scglib")" and my c/h files have "void init_scglib(void);" <pallagun>maybe there is some cache someplace I'm not properly wiping. <dsmith-work>Can you tell if your init is being called? (like with a printf) <pallagun>no, there appears to be no print statement <dsmith-work>If this is in a .scm file, wrap your load-extension with (eval-when (load eval compile) (load-extension .. ..)) <pallagun>no, it does not. I fear there is something incredibly simple that I'm missing and I'm simply not seening it right now <pallagun>dsmith-work: in any case, I've got to head out. Thank you for the help! ***karswell` is now known as karswell