On 3 January 2006 at 17:46, Frederic Daniel Luc LEHOBEY wrote:
| Package: r-cran-gtools
| Version: 2.2.3-1
| Severity: important
| 
| Hi,
| 
| When using r-cran-gtools on non Linux-i386 architectures a library 
| loading failure is experienced, like:
| 
| ** R
| ** preparing package for lazy loading
| Error in dyn.load(x, as.logical(local), as.logical(now)) : 
|       unable to load shared library 
| '/usr/lib/R/site-library/gtools/libs/gtools.so':
|   libc.so.6: cannot open shared object file: No such file or directory
| Execution halted

Unsurprisingly as the sources contain a src/ directory with a C file.  This
is entirely my mistake -- I'll fix that this evening and make it
"Architecture: any" as it needs to be.

Thanks for catching this!  Just shows that the humanly-maintained packages
can in fact be worse than the autobuild cran2deb packages ;-)

Dirk

| on kfreebsd-i386 architecture and:
| 
| ** R
| ** preparing package for lazy loading
| Error in dyn.load(x, as.logical(local), as.logical(now)) : 
|       unable to load shared library 
| '/usr/lib/R/site-library/gtools/libs/gtools.so':
|   /usr/lib/R/site-library/gtools/libs/gtools.so: ELF file data encoding 
| not big-endian
| Execution halted
| 
| on sparc and powerpc architectures.
| 
| It seems related to the following lintian error:
| http://lintian.debian.org/reports/mDirk_Eddelbuettel.html#gtools
| 
| Thanks,
| Frederic
| 
| -- System Information:
| Debian Release: testing/unstable
| Architecture: kfreebsd-i386 (i686)
| Shell:  /bin/sh linked to /bin/bash
| Kernel: GNU/kFreeBSD 5.4-1-486
| Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
| 
| Versions of packages r-cran-gtools depends on:
| ii  r-base-core                   2.2.1-1    GNU R core of statistical 
computin
| 
| r-cran-gtools recommends no packages.
| 
| -- no debconf information
| 

-- 
Hell, there are no rules here - we're trying to accomplish something. 
                                                  -- Thomas A. Edison


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to