On 12-05-08 1:46 AM, Joshua Wiley wrote:
Hi All,
I just downloaded the source tar ball (Revision: 59324 Last Changed
Date: 2012-05-07) and tried to compile on a Win x64 system. I am
using Rtools version 2.15.0.1919. The only change I make is changing
MkRules.dist -> MkRules.local and setting
I recently submit a package called QuasiSeq. The package source and
Windows binary worked fine, but the MacOS X binary failed. The bottom of
the CRAN page for QuasiSeq shows
Downloads:
Package source: QuasiSeq_1.0-1.tar.gz
MacOS X binary: not available, see check log.
Windows binary
On Tue, May 8, 2012 at 3:48 AM, Duncan Murdoch wrote:
> On 12-05-08 1:46 AM, Joshua Wiley wrote:
>>
>> Hi All,
>>
>> I just downloaded the source tar ball (Revision: 59324 Last Changed
>> Date: 2012-05-07) and tried to compile on a Win x64 system. I am
>> using Rtools version 2.15.0.1919. The on
Steven,
On May 7, 2012, at 1:24 PM, Steven Lund wrote:
> I recently submit a package called QuasiSeq. The package source and
> Windows binary worked fine, but the MacOS X binary failed. The bottom of
> the CRAN page for QuasiSeq shows
>
> Downloads:
> Package source: QuasiSeq_1.0-1.tar.gz
On 5/8/2012 8:44 AM, Simon Urbanek wrote:
Steven,
On May 7, 2012, at 1:24 PM, Steven Lund wrote:
I recently submit a package called QuasiSeq. The package source and
Windows binary worked fine, but the MacOS X binary failed. The bottom of
the CRAN page for QuasiSeq shows
Downloads:
Package
This time it was a similar error on a different file. Now fixed.
Duncan Murdoch
On 08/05/2012 11:20 AM, Joshua Wiley wrote:
On Tue, May 8, 2012 at 3:48 AM, Duncan Murdoch wrote:
> On 12-05-08 1:46 AM, Joshua Wiley wrote:
>>
>> Hi All,
>>
>> I just downloaded the source tar ball (Revision:
On May 8, 2012, at 11:56 AM, Martin Morgan wrote:
> On 5/8/2012 8:44 AM, Simon Urbanek wrote:
>> Steven,
>>
>> On May 7, 2012, at 1:24 PM, Steven Lund wrote:
>>
>>> I recently submit a package called QuasiSeq. The package source and
>>> Windows binary worked fine, but the MacOS X binary failed
The original post below refers to an issue that arose with glmnet. It
has since been fixed but the underlying problem (I believe) is a bug in
gcc/gfortran 2.6.3 toolchain. Here is a reproducible example, test.f90.
program dblbug
real :: x, y
x=2
y=exp(dble(x))
end program dblbug
Compile
