Skip to content

Problem configuring R-patched

7 messages · Kevin E. Thorpe, Gavin Simpson, Duncan Murdoch +1 more

#
I downloaded R-patched (2005-08-04) from CRAN today.
I ran ./configure --enable-R-shlib

I received the error message:

checking for recommended packages... no
configure: error: Some of the recommended packages are missing
   Use --without-recommended-packages if this was intentional

I built a previous version of R-patched successfully on my system
which is running the SuSE 9,2 Pro Linux distribution.  I untarred the
tar ball into the same directory I did my last build on in case that's
important.

The only other differences between this attempt and my successful build
are:

1. I did not use --enable-R-shlib last time.
2. I found and installed the blas libraries for this build.

Have I messed up or made an erroneous assumption along the way?

Thanks
#
On Thu, 2005-08-04 at 14:57 -0400, Kevin E. Thorpe wrote:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
So was this intentional?
Yes and No. You obviously haven't compiled R recently. If you haven't
got the recommended packages in the source you are compiling, configure
now gives an error, which quite clearly states (and you've quoted it in
your email!) that it cannot find (some of) the recommended packages.

A solution - again given by the error message you quote! - is:

./configure --enable-R-shlib --without-recommended-packages
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

That should clear things up.

Other wise you need to cd to the R directory (where you have the source
code), and then execute ./tools/rsync-recommended and then run your
configure command.

HTH

G
#
Gavin Simpson wrote:
No, it wasn't.
Actually, I compiled it about a week ago.  Here is my current version.

 > version
          _
platform i686-pc-linux-gnu
arch     i686
os       linux-gnu
system   i686, linux-gnu
status   Patched
major    2
minor    1.1
year     2005
month    07
day      28
language R

When I compiled that version, I did my "tar xzf" to a clean directory
and did not receive that error.
I realise that would clear it up.  I was puzzled why I got this message
in the first place, given I didn't get it last week.
Thanks for the rsync tip.
#
Kevin E. Thorpe wrote:
I believe there are two kinds of tar files.  The daily snapshots don't 
include the recommended packages, the releases do.

Or perhaps the test is a recent addition.

Duncan Murdoch
#
Duncan Murdoch wrote:
Both versions were R-patched.tar.gz as opposed to the devel sets which
looks like it's actually a link to the most recent.  Maybe I incorrectly
assumed that the patched tarballs contained the recommended packages.
Anyway, running rsync-recommended did the trick.

Thanks
#
Sorry to chime in a bit late here..

        
Kevin> Duncan Murdoch wrote:
>> Kevin E. Thorpe wrote:
>>
>>> Gavin Simpson wrote:
>>> 
    >>>> On Thu, 2005-08-04 at 14:57 -0400, Kevin E. Thorpe
>>>> wrote:
>>>> 
    >>>> 
    >>>>> I downloaded R-patched (2005-08-04) from CRAN today.
    >>>>> I ran ./configure --enable-R-shlib
    >>>>> 
    >>>>> I received the error message:
    >>>>> 
    >>>>> checking for recommended packages... no configure:
    >>>>> error: Some of the recommended packages are missing
    >>>>> Use --without-recommended-packages if this was
    >>>>> intentional
    >>>> 
    >>>> 
    >>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ So was this intentional?
    >>> 
    >>> 
    >>> 
    >>> No, it wasn't.
    >>> 
    >>> 
    >>>>> I built a previous version of R-patched successfully
    >>>>> on my system which is running the SuSE 9,2 Pro Linux
    >>>>> distribution.  I untarred the tar ball into the same
    >>>>> directory I did my last build on in case that's
    >>>>> important.
    >>>>> 
    >>>>> The only other differences between this attempt and my
    >>>>> successful build are:
    >>>>> 
    >>>>> 1. I did not use --enable-R-shlib last time.  2. I
    >>>>> found and installed the blas libraries for this build.
    >>>>> 
    >>>>> Have I messed up or made an erroneous assumption along
    >>>>> the way?
    >>>> 
    >>>> 
    >>>> 
    >>>> Yes and No. You obviously haven't compiled R
    >>>> recently. If you haven't got the recommended packages
    >>>> in the source you are compiling, configure now gives an
    >>>> error, which quite clearly states (and you've quoted it
    >>>> in your email!) that it cannot find (some of) the
    >>>> recommended packages.
    >>> 
    >>> 
    >>> 
    >>> Actually, I compiled it about a week ago.  Here is my
    >>> current version.
    >>> 
    >>> > version _ platform i686-pc-linux-gnu arch i686 os
    >>> linux-gnu system i686, linux-gnu status Patched major 2
    >>> minor 1.1 year 2005 month 07 day 28 language R
    >>> 
    >>> When I compiled that version, I did my "tar xzf" to a
    >>> clean directory and did not receive that error.
    >>> 
    >>> 
    >>>> A solution - again given by the error message you
    >>>> quote! - is:
    >>>> 
    >>>> ./configure --enable-R-shlib
    >>>> --without-recommended-packages
    >>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    >>>> 
    >>>> That should clear things up.
    >>> 
    >>> 
    >>> 
    >>> I realise that would clear it up.  I was puzzled why I
    >>> got this message in the first place, given I didn't get
    >>> it last week.
    >> 
    >> 
    >> I believe there are two kinds of tar files.  The daily
    >> snapshots don't include the recommended packages, the
    >> releases do.

eeehm, no: The daily snapshots do contain the recommended packages,
and have for quite a while now.

    >> Or perhaps the test is a recent addition.

only for a pretty generous definition of "recent".

To be honest, I don't know what Kevin's problem could be.

The daily snapshots are really produced here at ETH Zurich and
daily mirrored from here to CRAN. I can see that the 
	 R-patched_2005-08-04.tar.gz
does contain the recommended packages.

Maybe your download wasn't completed; your disk full; or you
have a gnome in your computer who occasionally deletes some of
your files?  I've had similar feelings a few times in the
past...

    Kevin> Both versions were R-patched.tar.gz as opposed to the
    Kevin> devel sets which looks like it's actually a link to
    Kevin> the most recent.  Maybe I incorrectly assumed that

    Kevin> Maybe I incorrectly assumed that the patched tarballs
    Kevin> contained the recommended packages.

actually that was a correct assumption.

Martin Maechler, ETH Zurich
#
Martin Maechler wrote:
I still don't know why it didn't work observe (sorry for the wrapping):

kevin at rho:/home/src> tar tvzf R-patched.tar.gz | grep Recommended
drwxr-xr-x local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/
-rw-r--r-- local/local    2394 2005-04-18 08:51:32 
R-patched/src/library/Recommended/Makefile.in
-rw-r--r-- local/local      20 2005-04-18 08:51:32 
R-patched/src/library/Recommended/.cvsignore
-rw-r--r-- local/local   25656 2005-04-18 08:58:17 
R-patched/src/library/Recommended/KernSmooth_2.22-15.tar.gz
-rw-r--r-- local/local  465529 2005-07-28 11:45:14 
R-patched/src/library/Recommended/VR_7.2-17.tar.gz
-rw-r--r-- local/local  179895 2005-07-28 11:45:14 
R-patched/src/library/Recommended/boot_1.2-23.tar.gz
-rw-r--r-- local/local  190975 2005-07-03 11:45:11 
R-patched/src/library/Recommended/cluster_1.10.1.tar.gz
-rw-r--r-- local/local  273520 2005-07-14 11:45:08 
R-patched/src/library/Recommended/foreign_0.8-9.tar.gz
-rw-r--r-- local/local  205131 2005-07-27 11:45:14 
R-patched/src/library/Recommended/lattice_0.12-1.tar.gz
-rw-r--r-- local/local  240276 2005-07-12 11:46:13 
R-patched/src/library/Recommended/mgcv_1.3-4.tar.gz
-rw-r--r-- local/local  662143 2005-07-26 11:45:13 
R-patched/src/library/Recommended/nlme_3.1-62.tar.gz
-rw-r--r-- local/local  110072 2005-04-19 11:45:20 
R-patched/src/library/Recommended/rpart_3.1-23.tar.gz
-rw-r--r-- local/local  846737 2005-06-10 11:45:23 
R-patched/src/library/Recommended/survival_2.18.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/VR.tgz -> VR_7.2-17.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/boot.tgz -> boot_1.2-23.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/cluster.tgz -> cluster_1.10.1.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/foreign.tgz -> foreign_0.8-9.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/KernSmooth.tgz -> 
KernSmooth_2.22-15.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/lattice.tgz -> lattice_0.12-1.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/nlme.tgz -> nlme_3.1-62.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/mgcv.tgz -> mgcv_1.3-4.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/rpart.tgz -> rpart_3.1-23.tar.gz
lrwxrwxrwx local/local       0 2005-08-03 20:45:50 
R-patched/src/library/Recommended/survival.tgz -> survival_2.18.tar.gz


It appears to me that the recommended packages were in the tarball.

I suppose it is largely immaterial now given I have successfully
re-built R.

Thanks your help.