Hi Dirk,
An important update to my message:
I called install.packages("nloptr") and I get exactly the same error. So I
think that something with my R and/or gcc installation is not correct. When I
install nloptr on the linux server of our cluster all runs fine. The point,
that I can build the nlopt library with my gcc compiler makes me hope to find
the error in the R installation (R-patched 3.0.1, although I built the gcc with
--disable-static).
I have to find the error in my installation. The way you proposed should work.
Thanks again for your help!
Best
Simon
On Sep 5, 2013, at 1:37 PM, Dirk Eddelbuettel <[email protected]> wrote:
>
> Simon,
>
> On 5 September 2013 at 12:44, Simon Zehnder wrote:
> | Hi Dirk,
> |
> | I was able to reconstruct my System this night and I immediately tried your
> suggestions:
> |
> | ii) Either using an absolute path nor repositioning the linking did work in
> my case.
>
> Well then you need to try something else. I would construct a two-file
> library (as a static build) and a two-file R package to load it, in order to
> work it out. It is doable; but I tend to have my code organized in a
> different way.
>
> No other immediate suggestion, sorry,
>
> Dirk
>
> --
> Dirk Eddelbuettel | [email protected] | http://dirk.eddelbuettel.com
_______________________________________________
Rcpp-devel mailing list
[email protected]
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
