On Mon, Mar 21, 2011 at 11:19 PM, Prof Brian Ripley
wrote:
> This is a bug in the package: you are required to quote paths in
> Makefiles, e.g. to allow for spaces in the path.
>
> And let's knock the issue of forward and backwards slashes on the head:
> they are equivalent on Windows. Despite yo
This is a bug in the package: you are required to quote paths in
Makefiles, e.g. to allow for spaces in the path.
And let's knock the issue of forward and backwards slashes on the
head: they are equivalent on Windows. Despite your perjorative
comments, the supplied value of R_HOME is valid.
On 03/21/2011 07:22 PM, Simon Urbanek wrote:
On Mar 21, 2011, at 9:07 PM, Dan Tenenbaum wrote:
Hello,
I have come across two separate packages that have a Makefile in inst/doc
which use the R_HOME variable.
In both cases, the path to R_HOME gets munged in such a way that commands
that includ
On Mon, Mar 21, 2011 at 7:22 PM, Simon Urbanek
wrote:
>
> On Mar 21, 2011, at 9:07 PM, Dan Tenenbaum wrote:
>
> > Hello,
> >
> > I have come across two separate packages that have a Makefile in inst/doc
> > which use the R_HOME variable.
> >
> > In both cases, the path to R_HOME gets munged in suc
On Mar 21, 2011, at 9:07 PM, Dan Tenenbaum wrote:
> Hello,
>
> I have come across two separate packages that have a Makefile in inst/doc
> which use the R_HOME variable.
>
> In both cases, the path to R_HOME gets munged in such a way that commands
> that include R_HOME fail on Windows:
>
> For
Hello,
I have come across two separate packages that have a Makefile in inst/doc
which use the R_HOME variable.
In both cases, the path to R_HOME gets munged in such a way that commands
that include R_HOME fail on Windows:
For example, one Makefile, for the xmapcore package (
https://hedgehog.fh
