But its value to you and whether or not you would pay for it is a
completely separate matter from whether or not they are violating the
R license by selling their R collection. I imagine a discussion of
the latter is on-topic for this list, less so for the former, I'd
imagine.
Cyrus
On A
ion is stored
> that someone did not check the consequences of. It will be fixed
> shortly (I am testing a fix right now). Meanwhile,
>
> make; make; make install
>
> works.
>
> On Sat, 7 Jan 2006, Cyrus Harmon wrote:
>
>> I'm trying to build from the lates
Mar 7, 2006, at 3:46 PM, Seth Falcon wrote:
> Cyrus Harmon <[EMAIL PROTECTED]> writes:
>
>> Dear r-devel,
>>
>> Sorry to trouble the list with this, but I've been beating my head
>> against the wall trying to figure out what's wrong. When I try to
Dear r-devel,
Sorry to trouble the list with this, but I've been beating my head
against the wall trying to figure out what's wrong. When I try to
connect to the R SVN server, I get the following message:
([EMAIL PROTECTED]):~/src/R$ svn co https://svn.r-project.org/R/trunk r-devel
svn: PROP
I'm trying to build from the latest SVN sources on Mac OS X 10.4.3
and I seem to be having a problem making the documentation.
When I do make install, i get the following:
([EMAIL PROTECTED]):~/src/R/r-devel/build-f95$ make install
make[1]: Nothing to be done for `front-matter'.
SVN-REVISION is
Dear r-devel,
When R has been installed in a non-standard location (or any location
where Apple's version of gcc isn't going to, by default, look for
frameworks specified with the -framework arg), builds of R packages
fail because the linker can't find the framework. The following patch
to
Dear r-devel,
Using the latest R-devel from SVN, when doing a make install, even
from a build directory, there is a recursive copy that attempts to
copy the .svn file to the framework include directory. The problem is
due to the fact that there is a reference to $srcdir in Makefile.in
tha
