Skip to content
Prev 5889 / 10988 Next

[Rcpp-devel] Rcpp.package.skeleton in 0.10.3 does not work correctly?

Hi Peng,

On your side, I don't understand why you're getting this output:

-I/Library/Frameworks/R.framework/Resources/include -DNDEBUG  -Wall
-I/usr/local/include -I"/Users/py/utility/R_user/Rcpp/include"   -fPIC
 -mtune=core2 -g -O2  -c rcpp_hello_world.cpp -o rcpp_hello_world.o
llvm-g++-4.2 -arch x86_64 -dynamiclib -Wl,-headerpad_max_install_names
-undefined dynamic_lookup -single_module -multiply_defined suppress
-L/usr/local/lib -L/usr/local/lib -o mypackage.so rcpp_hello_world.o >
Rcpp:::LdFlags() /Users/py/utility/R_user/Rcpp/lib/libRcpp.a> >
-F/Library/Frameworks/R.framework/.. -framework R -Wl,-framework
-Wl,CoreFoundation

ie, why is Rcpp:::LdFlags() getting tossed in there as-is rather than being
evaluated and inserting the libRcpp.a library location? Not to mention the
extraneous '>'s. Perhaps you've manually set the R_HOME environment
variable and it's out of sync with the location of your current R
installation?

It looks to me like there is something strange with how things are set up
on your machine, but it's difficult to diagnose what.

-Kevin
On Sat, May 25, 2013 at 6:19 AM, Dirk Eddelbuettel <edd at debian.org> wrote: