Thanks Professor Dalgard.
If you have a different way to fix the bug then I'd be happy to test
it.
Or whatever. I understand that maybe some data was being referenced
before it had been initialized. I could also support moving the
R_ProcessEvents call in another place, but it seems one would als
On 4/25/19 07:50, Tomas Kalibera wrote:
> On 4/20/19 10:39 PM, Pages, Herve wrote:
>> Hi,
>>
>> I was trying to update packages today on one of our MacOS servers, and
>> got this:
>>
>> > update.packages(ask=FALSE)
>>
>> There is a binary version available but the source version is
>> l
Hi Tomas,
On 4/23/19 2:59 PM, Thomas König wrote:
Hi,
there can be an issue with recent gcc where the system-installed "ar"
and "ranlib" commands cannot handle LTO binaries. On compilation, this
manifests itself with error messages claiming that they need extra
plugins.
Thanks for the repor
On 4/23/19 2:59 PM, Thomas König wrote:
Hi,
there can be an issue with recent gcc where the system-installed "ar"
and "ranlib" commands cannot handle LTO binaries. On compilation, this
manifests itself with error messages claiming that they need extra
plugins.
This can be fixed by using the co
On 4/20/19 10:39 PM, Pages, Herve wrote:
Hi,
I was trying to update packages today on one of our MacOS servers, and
got this:
> update.packages(ask=FALSE)
There is a binary version available but the source version is later:
binary source needs_compilation
gsl 1.9-10.3
On 4/25/19 2:20 PM, Pages, Herve wrote:
On 4/25/19 04:57, Tomas Kalibera wrote:
On 4/25/19 3:11 AM, Pages, Herve wrote:
Hi,
I was playing around with inotifywait (great tool!) to see the new
staged installation of source packages in action. In one terminal I'm
monitoring the create/delete/mov
On 4/25/19 04:57, Tomas Kalibera wrote:
> On 4/25/19 3:11 AM, Pages, Herve wrote:
>> Hi,
>>
>> I was playing around with inotifywait (great tool!) to see the new
>> staged installation of source packages in action. In one terminal I'm
>> monitoring the create/delete/move events of the installation
On 4/25/19 3:11 AM, Pages, Herve wrote:
Hi,
I was playing around with inotifywait (great tool!) to see the new
staged installation of source packages in action. In one terminal I'm
monitoring the create/delete/move events of the installation library with:
inotifywait -m --timefmt '%F %T' --
On 4/24/19 6:41 PM, Hugh Marera wrote:
> Some of us are learning about development in R and use R in our work
> data analysis pipelines. What is the best way to identify packages
> that currently have these C++ problems? I would like to be able to
> help fix the bugs but more importantly not use
Hi,
I have tried to pinpoint potential problems which could lead to the
LAPACK issues that are currently seen in R. I built the current R
trunk using
AR=gcc-ar RANLIB=gcc-ranlib ./configure --prefix=$HOME --enable-lto
--enable-BLAS-shlib=no --without-recommended-packages
and used this to fin
Some of us are learning about development in R and use R in our work data
analysis pipelines. What is the best way to identify packages that
currently have these C++ problems? I would like to be able to help fix the
bugs but more importantly not use these packages in critical work
pipelines. Any C+
11 matches
Mail list logo