On 14 October 2006 at 20:29, Martin Michlmayr wrote:
| * Dirk Eddelbuettel <[EMAIL PROTECTED]> [2006-10-14 13:10]:
| > What happens when you try this in the chroot:
| 
| This is on amd64 now:
| 
| sh-3.1# ldd /usr/lib/R/site-library/fSeries/libs/fSeries.so
|         libRlapack.so => not found
|         libgfortran.so.1 => /usr/lib/libgfortran.so.1 (0x00002aaaab06a000)

That's the one then as I had

        libgfortran.so.0 => /usr/lib/libgfortran.so.0 (0xb747f000)

How could that have slipped? Whose shlibs file do we need to look at?

|         libm.so.6 => /lib/libm.so.6 (0x00002aaaab201000)
|         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaab383000)
|         libR.so => not found
|         libc.so.6 => /lib/libc.so.6 (0x00002aaaab491000)
|         /lib64/ld-linux-x86-64.so.2 (0x0000555555554000)
| sh-3.1# dpkg -l r-base-core libgfortran0 r-cran-fseries
| No packages found matching libgfortran0.
| Desired=Unknown/Install/Remove/Purge/Hold
| | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
| |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: 
uppercase=bad)
| ||/ Name                Version             Description
| 
+++-===================-===================-======================================================
| ii  r-base-core         2.4.0-1             GNU R core of statistical 
computing language and envir
| ii  r-cran-fseries      221.10065-3         GNU R package for financial 
engineering -- fSeries
| sh-3.1#

Yes, we discovered an implicit (Build-)Depends on libgfortran0.  

As I will rebuilt all these Rmetrics packages in the next few days (once the
new r-cran-fecofin is in the archive), how can I make sure the same problem
won't bite us on the move from gfortran 4.1 to 4.2, 4.3, ... and beyond?

Dirk

-- 
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