search for: _optional_

...warning flags are detected, such as -Werror, because they are >> non-portable. This appears to have been added in this commit: >> https://github.com/wch/r-source/commit/2e80059 > > > That is not the canonical R sources. And your description seems wrong: > there is now an _optional_ check controlled by an environment variable, > primarily for CRAN checks. Are the canonical R sources made available in such a way that one can link to them? Hadley -- http://hadley.nz

On recent builds of R-devel, R CMD check gives a WARNING when some compiler warning flags are detected, such as -Werror, because they are non-portable. This appears to have been added in this commit: https://github.com/wch/r-source/commit/2e80059 I'm working on a package where these compiler warning flags are present in a Makefile generated by a configure script -- that is, the configure

...in this email thread. But, I do _NOT_ recommend updating Slackware to use Syslinux 6.xx, even if this means not being able to use an updated isohybrid tool. What I mentioned about Syslinux was for you, to optionally and *temporarily* use 6.03-pre19 (or newer) ONLY for a TEST. This would be an _optional_ test, only in case either the other changes (mkisofs arguments and version update) or an alternative method, would not be enough. According to your recent feedback and later Thomas' email, this test seems to be currently unneeded. > > > According to the subject of this email thr...

...message there, and because I see it every time I visit the repository. If you have a good way of pointing people to the changes made in a commit with the canonical R sources, please let us know. I and many others would be happy to use it. > And your description seems wrong: > there is now an _optional_ check controlled by an environment variable, > primarily for CRAN checks. The check is "optional", but not for packages submitted to CRAN. >> I'm working on a package where these compiler warning flags are >> present in a Makefile generated by a configure script -- t...

I''m getting this message (subject line) in daemon.log every time I start or restart xend. I''m not sure if this is related to the fact that I cannot boot up my Windows domU from a VHD file. The Windows domU was working fine with Xen 4.0.0 (with 2.6.32.14 dom0 kernel). When I upgraded to Xen 4.0.1-rc4 (with 2.6.32.16 dom0 kernel), I can no long boot the Windows domU from VHD. The

...G when some > compiler warning flags are detected, such as -Werror, because they are > non-portable. This appears to have been added in this commit: > https://github.com/wch/r-source/commit/2e80059 That is not the canonical R sources. And your description seems wrong: there is now an _optional_ check controlled by an environment variable, primarily for CRAN checks. > I'm working on a package where these compiler warning flags are > present in a Makefile generated by a configure script -- that is, the > configure script detects whether the compiler supports these flags, >...

...d, such as -Werror, because they are >>> non-portable. This appears to have been added in this commit: >>> https://github.com/wch/r-source/commit/2e80059 >> >> >> That is not the canonical R sources. And your description seems wrong: >> there is now an _optional_ check controlled by an environment variable, >> primarily for CRAN checks. > > Are the canonical R sources made available in such a way that one can > link to them? Yes, the sources are available. To link to revision 73909 of R on the trunk branch (which I think is the one referr...

In order to support the eventual MFC of a limited and experimental acpi(4) driver from -CURRENT, I have merged a few changes from -CURRENT to -STABLE including: - Power management interface (subr_power.c) - pmtimer(4) driver. Unlike -CURRENT this driver does not require 'device pmtimer' in the kernel config so that existing kernel configs do not have to be changed. - Updated

[This email is either empty or too large to be displayed at this time]

...nimal services and hence would be minimally vulnerable. The times have changed though and I will look into adding WebSVN to svn.r-project.org as one of the first things in 2018. Martin Maechler >> >>> And your description seems wrong: there is now an >>> _optional_ check controlled by an environment variable, >>> primarily for CRAN checks. >> >> The check is "optional", but not for packages submitted >> to CRAN. >> >> >>>> I'm working on a package where these compi...

hello everyone, i'm trying to run a postgresql service on my newly-installed centos4 box. i have been able to recreate my users, set up the permissions, and restore the database dump. also, i can already log-in to my databases. there is, however, one annoying problem. whenever i type \du (or \d or \l) on the psql prompt, i get the following error: ERROR: relation

...ty is that someone could set up (or already has?) one of the web viewers (WebSVN, etc.) for the real repository. That would be better for those of us who are SVN users, but probably harder for Git users. Duncan Murdoch > >> And your description seems wrong: >> there is now an _optional_ check controlled by an environment variable, >> primarily for CRAN checks. > > The check is "optional", but not for packages submitted to CRAN. > > >>> I'm working on a package where these compiler warning flags are >>> present in a Makefile gene...

HI, On 29/07/2014 22:23, Ady wrote: > Even without such "Mac" hardware at hand, it might still be helpful > to test mkisofs 3.01a24 and then check the resulting ISO image. > Perhaps Didier can update his current version of mkisofs and retry > with his current scripts/receipts. I will upgrade the cdrtools package from 3.01a17 to 3.01a24 in the coming days and see what I

> Hi, > > > I don't understand why you say "*But* the El Torito...". I don't see > > a difference with what the mkisofs manual says. > > The manual announces "Mac" for Apple Mac. > The program obviously writes Platform Id 1 in this case. > The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". > In the sum this

...he Git desktop clients also support Git SVN (https://git-scm.com/docs/git-svn), for compatibility, which offers Git users an alternative to using a dedicated desktop SVN client. Regards, Marc > >>> >>>> And your description seems wrong: there is now an >>>> _optional_ check controlled by an environment variable, >>>> primarily for CRAN checks. >>> >>> The check is "optional", but not for packages submitted >>> to CRAN. >>> >>> >>>>> I'm working on a package where these compi...

Hi Emil, On Wed, 21 Sep 2016, Emil Velikov wrote: > On 20 September 2016 at 09:32, Peter Griffin <peter.griffin at linaro.org> wrote: > > Hi Emil, > > > > On Tue, 20 Sep 2016, Emil Velikov wrote: > > > >> On 5 September 2016 at 14:16, Peter Griffin <peter.griffin at linaro.org> wrote: > >> > ST_SLIM_REMOTEPROC must select REMOTEPROC,

Hi Emil, On Wed, 21 Sep 2016, Emil Velikov wrote: > On 20 September 2016 at 09:32, Peter Griffin <peter.griffin at linaro.org> wrote: > > Hi Emil, > > > > On Tue, 20 Sep 2016, Emil Velikov wrote: > > > >> On 5 September 2016 at 14:16, Peter Griffin <peter.griffin at linaro.org> wrote: > >> > ST_SLIM_REMOTEPROC must select REMOTEPROC,

...(https://git-scm.com/docs/git-svn), for compatibility, which offers Git users an alternative to using a dedicated desktop SVN client. > > Regards, > > Marc > > >> >>>> >>>>> And your description seems wrong: there is now an >>>>> _optional_ check controlled by an environment variable, >>>>> primarily for CRAN checks. >>>> >>>> The check is "optional", but not for packages submitted >>>> to CRAN. >>>> >>>> >>>>>> I'm working on a...