Re: [Bioc-devel] Problem with non-portable compiler flags on package test

2019-04-13 Thread Aaron Lun
To contribute another data point on the use of architecture-specific compilation settings, see the discussion at: https://www.mail-archive.com/bioc-devel@r-project.org/msg10525.html This discrepancy took two months to track down. Two months! During my holidays! And it wasn't even my fault! S

Re: [Bioc-devel] Problem with non-portable compiler flags on package test

2019-04-12 Thread Martin Morgan
Your configure outsmarts the check system, so your options are to omit the flags or to live with the warning. Either solution is fine with Bioconductor. Martin On 4/12/19, 4:17 AM, "Bioc-devel on behalf of Jochen Knaus" wrote: Hi everybody, for our new R package "Netboost" we ha

[Bioc-devel] Problem with non-portable compiler flags on package test

2019-04-12 Thread Jochen Knaus
Hi everybody, for our new R package "Netboost" we have a problem about non portable compiler flags. Basically we support AVX in our own C++ code (using compiler intrinsics to use the AVX units). Of course we have a non-AVX code path. For building we use autotools and configure to determine at