[Rcpp-devel] mzR and Rcpp - could not find function "errorOccured"
sneumann at ipb-halle.de
Fri Jun 29 15:43:48 CEST 2012
what is the outcome of this ? In which constellation does the problem occur ?
Do we need to bump the minimum Rcpp version in mzR dependenceis ?
From: rcpp-devel-bounces at lists.r-forge.r-project.org [rcpp-devel-bounces at lists.r-forge.r-project.org] on behalf of Laurent Gatto [lg390 at cam.ac.uk]
Sent: 27 June 2012 10:09
To: Davor Cubranic
Cc: rcpp-devel at r-forge.wu-wien.ac.at
Subject: Re: [Rcpp-devel] mzR and Rcpp - could not find function "errorOccured"
On 26 June 2012 21:42, Davor Cubranic <cubranic at stat.ubc.ca> wrote:
> Doesn't Rcpp 2.11 require 2.15.1, and the computers on which you had problems had 2.15?
> Also, you don't say if you tried rebuilding your package, or if you just continued using the same binary. It is possible that since Rcpp API changed, the missing symbol is detected by the dynamic link loader and so aborts loading mzR. (Not sure why it would work on some platforms and not others -- maybe dynamic linking is more tolerant than on others.)
I have never had this myself on linux, building from source. These
issues have been reported by users (one of which was using 2.15 but
did not specify the package versions), and I have been able to
reproduce getting the windows binary packages build on the
I will try with fresh binaries. Thank you very much for your help!
> On 2012-06-26, at 12:31 PM, Laurent Gatto wrote:
>> On 26 June 2012 20:17, Dirk Eddelbuettel <edd at debian.org> wrote:
>>> On 26 June 2012 at 19:39, Laurent Gatto wrote:
>>> | Dear all,
>>> I am confused. So in general no error on Linux and on some versions of
>>> Windows and OS X, but an error on other versions of OS X and Windows?
>>> Could this be as simple as required a rebuild of the related packaged (eg
>>> Rcpp and mzR) ?
>>> | I am assuming that this is related to Rcpp, but am pretty much stuck.
>>> | Could this be related to "errorOccuredSym never used and commented
>>> | out" from the ChangeLog?
>>> From what I recall I simply followed a warning from g++ about an unused var
>>> which I commented out in src/Evaluator.cpp. You could always fetch an older
>>> src/Evaluator.cpp and drop it in and see what happens.
>>> We'd need something reproducible, preferable on a platform I have access too.
>> I understand. I am confused too and not sure what to do about these
>> sporadic reports. Will hopefully find more compelling data and report
>>> | Any help greatly appreciated.
>>> | Best wishes,
>>> | Laurent
>>> |  http://bioconductor.org/packages/2.10/bioc/html/mzR.html
>>> |  http://stackoverflow.com/questions/11181691/r-bioconductor-mzr-library-load-error
>>> |  https://stat.ethz.ch/pipermail/bioconductor/2012-June/046496.html
>>> |  http://bioconductor.org/checkResults/2.10/bioc-LATEST/moscato2-NodeInfo.html
>>> |  http://bioconductor.org/checkResults/2.10/bioc-LATEST/petty-NodeInfo.html
>>> |  http://bioconductor.org/checkResults/2.10/bioc-LATEST/lamb2-NodeInfo.html
>>> | _______________________________________________
>>> | Rcpp-devel mailing list
>>> | Rcpp-devel at lists.r-forge.r-project.org
>>> | https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
>>> Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com
>> Rcpp-devel mailing list
>> Rcpp-devel at lists.r-forge.r-project.org
Cambridge Centre for Proteomics
Rcpp-devel mailing list
Rcpp-devel at lists.r-forge.r-project.org
More information about the Rcpp-devel