steve@thelaptop:~/module$ make test_static
cd ccode && make
make[1]: Entering directory `/home/steve/module/ccode'
gcc -shared -Wl,-soname,libpfq -Wl,-E -Wl,-rpath,/usr/lib/perl/5.8.7/C
+ORE -o libpfq.so.1 socket.o services.o -lc
make[1]: Leaving directory `/home/steve/module/ccode'
rm -rf blib/arch/auto/module/module.a
cp ccode/libpfq blib/arch/auto/module/module.a
/usr/bin/ar cr blib/arch/auto/module/module.a module.o && : blib/arch/
+auto/module/module.a
/usr/bin/ar: blib/arch/auto/module/module.a: File format not recognize
+d
make: *** [blib/arch/auto/module/module.a] Error 1
I've just tried it with a diagnostics enabled as well and it has replied with:
Compilation failed in require at test.pl line 5 (#1)
(F) The module you tried to load failed to load a dynamic extensio
+n. This
may either mean that you upgraded your version of perl to one that
+ is
incompatible with your old dynamic extensions (which is known to h
+appen
between major versions of perl), or (more likely) that your dynami
+c
extension was built against an older version of the library that i
+s
installed on your system. You may need to rebuild your old dynamic
extensions.
Which library is 'the library'? Do they mean libc or some library in perl itself? There's nothing in perlxs or perlxstut that says I should link against a specific library.
The C functions operate on mail queues- deferring and deleting messages and so on.
Oh, and thanks to the people who set me straight (and edited my post) about formatting- I was going to use code tags but I didn't see it in the list of allowed tags. I should always remember to read the next line as well. |