[Rd] Problem with WARNING...headers with CRLF line endings
cstrato
cstrato at aon.at
Sat Sep 25 15:02:43 CEST 2010
Dear Herve,
I have just tested the modification of Makefile.win:
clean:
rm -f $(MYOBJ) *.a *.d *.rc xpsLinkDef.h
and it was sufficient to eliminate the warning message.
Thus R CMD check seems indeed to run the clean step.
I have just uploaded the new version to BioC2.7.
Best regards
Christian
On 9/15/10 11:53 PM, Hervé Pagès wrote:
> On 09/15/2010 01:51 PM, Dirk Eddelbuettel wrote:
>>
>> On 15 September 2010 at 22:39, cstrato wrote:
>> | Dear Duncan, dear Herve,
>> |
>> | Thank you both for your help and suggestions. I think that you are both
>> | right:
>> |
>> | In principle I do not want to put these files in the source tarball
>> (and
>> | I did not in the past), however because of the way R CMD check works
>> | this seems to be the only possibility to get rid of the warning
>> message.
>> |
>> | I agree that it is weird to get this warning message although these
>> | files are not in the source tarball.
>> |
>> | Since I have a Makefile, as Herve mentions, I can try to remove these
>>
>> If you have a Makefile, then you have implicit rules as well as explicit
>> ones. That is how the file gets created.
>>
>> Now modify the rules and insert another layer which will do the
>> filtering. As
>> the saying goes: "there is no problem that cannot be solved by adding
>> another layer of indirection". Instead of requiring the generated file,
>> require the generated and filtered file.
>>
>> | files in the clean step, which currently is:
>> |
>> | clean:
>> | rm -f $(MYOBJ) *.a *.d *.rc
>> |
>> | I will try to change this part but I am not sure if this will solve the
>> | problem.
>>
>> I fear that the clean step runs too late.
>
> But shouldn't 'R CMD check' run the clean step (if it runs it at all)
> right after the 'R CMD INSTALL' step?
>
> Cheers,
> H.
>
>
More information about the R-devel
mailing list