Displaying 4 results from an estimated 4 matches for "xsloader".
2011 Oct 18
2
Fried Email Server! Perl Problem
...com:210.76.164.235::2804
@400000004e9ddbd81c826894 Can't load '/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/auto/DB_File/DB_File.so' for module DB_File: libdb-4.3.so: failed to map segment from shared object: Cannot allocate memory at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/XSLoader.pm line 70.
@400000004e9ddbd81c827c1c? at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/DB_File.pm line 251
@400000004e9ddbd81c828004 Compilation failed in require at /var/qmail/bin/qmail-scanner-queue.pl line 480.
@400000004e9ddbd81c8287d4 BEGIN failed--compilation aborted at /var/qmail/bin/qma...
2007 Aug 03
2
Problem with making dll under Windows
Dear all,
I have problems to compile a DLL for Windows XP with R version 2.5.1 (2007-06-27).
See output below:
C:\AZ_DATEN\C, C++\BE_speedup>R CMD SHLIB dmypow.c
Goto undefined subroutine &DynaLoader::bootstrap_inherit at C:\Programme\R\R-2.5
.1\share\perl/XSLoader.pm line 80.
Compilation failed in require at c:/Programme/Perl/lib/IO/Handle.pm line 262.
BEGIN failed--compilation aborted at c:/Programme/Perl/lib/IO/Handle.pm line 262
.
Compilation failed in require at c:/Programme/Perl/lib/IO/Seekable.pm line 101.
BEGIN failed--compilation aborted at c:/Progra...
2016 Feb 25
2
[PATCH] perl: Don't embed API number in Sys::Guestfs.
...is unrelated to the
+# real libguestfs version. If you want to find the libguestfs
+# library version, use $g->version. If you want to test if
+# APIs/parameters are present, use %%guestfs_introspection.
use vars qw($VERSION);
-$VERSION = '0.%d';
+$VERSION = '1.0';
require XSLoader;
XSLoader::load ('Sys::Guestfs');
-" max_proc_nr;
+";
(* Methods. *)
pr "\
--
2.5.0
2003 Aug 02
7
[2.6] Perl weirdness with ext3 and HTREE
Hi
I have mailed about this previously, but back then it was not
really confirmed, so I have let it be at that.
Anyhow, problem is that for some reason 2.5/2.6 ext3 with HTREE
support do not like what perl-5.8.0 does during installation.
It *seems* like one of the temporary files created during manpage
installation do not get unlinked properly, or gets into the
hash (this possible?) and cause