search for: winshlib

...TS in case the symbol name is the same as a linker keyword: - https://sourceware.org/binutils/docs/ld/Symbols.html#Symbols - https://msdn.microsoft.com/en-us/library/163abkbh.aspx I wasn't sure how that related specifically to what Rtools is using, but when I made the following change to winshlib.mk (double quotes around symbol names in tmp.def), I was able to compile code without issue and get symbols like BASE (or other keywords) exported. Kyle ## ${R_HOME}/share/make/winshlib.mk 6a7,8 > ADDQU = 's/[^ ][^ ]*/"&"/g' > 17c19 < $(NM) $^ | $(SED) -n $(...

Example input and output to reproduce this can be found at https://gist.github.com/jimhester/b7f05f50794c88e44b17. I tested this attempting to compile the [digest]( http://cran.r-project.org/web/packages/digest/index.html) package, `run.sh` and `run.bat` were both run in the package source directory on Ubuntu 14.01 and Windows 7 respectively. In particular while the `CFLAGS` values were properly

...I have litterally nothing, no output at all. (and R CMD INSTALL debug tells me, of course that the operation failed while calling R CMD SHLIB) I tried the command R CMD SHLIB -n, which gives me : make -f "C:/Trading/R/R-2.14.1/etc/i386/Makeconf" -f "C:/Trading/R/R-2.14.1/share/make/winshlib.mk" SHLIB= OBJECTS= So I had a closer look at these two files, and found some strange things in Makeconf, for example a variable LOCAL_SOFT with a d: path which has nothing to do with my configuration : LOCAL_SOFT = d:/RCompile/CRANpkg/extralibs/local Ok, the thing is, my Makeconf is strang...

...blem using 2.11.1). If I simply follow the instructions of the first reference I get lots of "cannot export / symbol not defined" errors because by default the leading underscore is stripped off during the shared library build process, specifically, all names in tmp.def (created in share/winshlib.mk) do not contain a leading underscore. If I modify share/winshlib.mk so that the leading underscore is not stripped everything works fine. Have I missed some documentation explaining what is going on here? Thanks, Dominick [[alternative HTML version deleted]]

Dear R-helpers, I tried to build a DLL like I have done so many times, but this time on my new machine, but it gives the erorr: (from cmd window) >R CMD SHLIB Boxcnt.f MAKE Version 5.2 Copyright (c) 1987, 2000 Borland Error c:/PROGRA~1/R/R-210~1.1/share/make/winshlib.mk 4: Command syntax error *** 1 errors during make *** The error is not in my Fortran file, because I also tried other files or even without any arguments (it gives the same error msg regardless). System: Windows Vista R 2.10.1 Rtools installed (version 2.11) thanks, Remko ------------------...

Under Windows the make include share/make/winshlib.mk uses nm to grab symbols from object files to insert into a module definition file tmp.def that is used to create a package DLL. This works fine provided the DLL is only used via exported function entry points, which is the case currently, I suspect. But the pattern SYMPAT (defined in Makeconf)...

...configure script It probably needs manual configuration ********************************************** ** libs *** arch - i386 Warning: running command 'make -f "Makevars" -f "C:/PROGRA~1/R/R-3.2.0/etc/i386/Makeconf" -f "C:/PROGRA~1/R/R-3.2.0/share/make/winshlib.mk" SHLIB="Rcartogram.dll" OBJECTS="Rcart.o cart.o"' had status 127 ERROR: compilation failed for package 'Rcartogram' * removing 'C:/Users/Milena/Documents/R/win-library/3.2/Rcartogram' Warning in install.packages : running command '"C:/PRO...

...s to what to do. When I type, "R CMD SHLIB foo.c" using the Command Prompt I get: make: *** No rule to make target 'foo.o', needed by 'foo.dll'. Stop. Warning message: running command 'make -f "C:/R/R-3.1.0/etc/x64/Makeconf" -f "C:/R/R-3.1.0/share/make/winshlib.mk" SHLIB="filename.dll" WIN=64 TCLBIN=64 OBJECTS="filename.o"' has status 2 NB: I am using R-3.1.0 and the most current Rtools suitable for R-3.1.0 as directed. To clarify, I installed R-3.1.0 (64-bit) on "C:\R\R-3.1.0". I installed Rtools to "C:\R\Rto...

...you > are unable to find another cygwin DLL. > make: *** [Models/Bart/LogitBartModel.o] Error 127 > Warning: running command 'make -f "Makevars" -f > "C:/R/R-34~1.0/etc/i386/Makeconf" -f > "C:/R/R-34~1.0/share/make/winshlib.mk <http://winshlib.mk>" -f > "C:/Users/john/Documents/.R/Makevars" CXX='$(CXX11) $(CXX11STD)' > CXXFLAGS='$(CXX11FLAGS)' CXXPICFLAGS='$(CXX11PICFLAGS)' > SHLIB_LDFLAGS='$(SHLIB_CXX11LDFLAGS)' SHLIB_LD='$(SHLI...

...is also suggested if you >> are unable to find another cygwin DLL. >> make: *** [Models/Bart/LogitBartModel.o] Error 127 >> Warning: running command 'make -f "Makevars" -f >> "C:/R/R-34~1.0/etc/i386/Makeconf" -f >> "C:/R/R-34~1.0/share/make/winshlib.mk" -f >> "C:/Users/john/Documents/.R/Makevars" CXX='$(CXX11) $(CXX11STD)' >> CXXFLAGS='$(CXX11FLAGS)' CXXPICFLAGS='$(CXX11PICFLAGS)' >> SHLIB_LDFLAGS='$(SHLIB_CXX11LDFLAGS)' SHLIB_LD='$(SHLIB_CXX11LD)' >> SHLIB="Bo...

...mmands, I get this output. I honestly have no clue whether this can be considered as something useful or not :-/ ``` > tools:::.shlib_internal(c('-n', 'hello.c')) make cmd is make -f "C:/PROGRA~1/R/R-43~1.1/etc/x64/Makeconf" -f "C:/PROGRA~1/R/R-43~1.1/share/make/winshlib.mk" SHLIB="hello.dll" WIN=64 TCLBIN= OBJECTS="hello.o" make would use gcc -I"C:/PROGRA~1/R/R-43~1.1/include" -DNDEBUG -I"C:/rtools43/x86_64-w64-mingw32.static.posix/include" -O2 -Wall -mfpmath=sse -msse2 -mstackrealign -c hello.c -o hello.o i...

...RNING: this package has a configure script It probably needs manual configuration ********************************************** ** libs Aviso: comando ejecutado 'make -f "Makevars.win" -f "C:/PROGRA~1/R/R-31~1.3/etc/x64/Makeconf" -f "C:/PROGRA~1/R/R-31~1.3/share/make/winshlib.mk" SHLIB="ncdf4.dll" WIN=64 TCLBIN=64 OBJECTS="ncdf.o ncdf2.o ncdf3.o src_ncdf4.o"' tiene estatus 127 ERROR: compilation failed for package 'ncdf4' * removing 'C:/Users/MRN/Documents/R/win-library/3.1/ncdf4' * restoring previous 'C:/Users/MRN/Docume...

...nstalled the cygwin distribution. Rebooting is also suggested if you are unable to find another cygwin DLL. make: *** [Models/Bart/LogitBartModel.o] Error 127 Warning: running command 'make -f "Makevars" -f "C:/R/R-34~1.0/etc/i386/Makeconf" -f "C:/R/R-34~1.0/share/make/winshlib.mk" -f "C:/Users/john/Documents/.R/Makevars" CXX='$(CXX11) $(CXX11STD)' CXXFLAGS='$(CXX11FLAGS)' CXXPICFLAGS='$(CXX11PICFLAGS)' SHLIB_LDFLAGS='$(SHLIB_CXX11LDFLAGS)' SHLIB_LD='$(SHLIB_CXX11LD)' SHLIB="Boom.dll" ' had status 2 ERRO...

...er Windows 'make all' and 'make recommended; (but not 'make distribution') can each be done in parallel. There are some question marks over how well the 'make; used on Windows works in parallel (we found one case where it worked incorrectly and had to rethink share/make/winshlib.mk) so it should be used with caution. Please give these new facilties a go and report (here) how you get on. -- Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 27286...

...ibution. Rebooting is also suggested if you > are unable to find another cygwin DLL. > make: *** [Models/Bart/LogitBartModel.o] Error 127 > Warning: running command 'make -f "Makevars" -f > "C:/R/R-34~1.0/etc/i386/Makeconf" -f > "C:/R/R-34~1.0/share/make/winshlib.mk" -f > "C:/Users/john/Documents/.R/Makevars" CXX='$(CXX11) $(CXX11STD)' > CXXFLAGS='$(CXX11FLAGS)' CXXPICFLAGS='$(CXX11PICFLAGS)' > SHLIB_LDFLAGS='$(SHLIB_CXX11LDFLAGS)' SHLIB_LD='$(SHLIB_CXX11LD)' > SHLIB="Boom.dll" ...

...have no > clue whether this can be considered as something useful or not :-/ > > ``` > > tools:::.shlib_internal(c('-n', 'hello.c')) > make cmd is > make -f "C:/PROGRA~1/R/R-43~1.1/etc/x64/Makeconf" -f > "C:/PROGRA~1/R/R-43~1.1/share/make/winshlib.mk" SHLIB="hello.dll" > WIN=64 TCLBIN= OBJECTS="hello.o" This can be considered good news. You have just successfully performed the job that is normally done by R CMD SHLIB when installing source packages or running inline C++ code. The environment variables, at least i...

? Thu, 31 Aug 2023 11:57:06 +0000 Christophe Bousquet <chr_bousquet at protonmail.com> ?????: > > tools::Rcmd('SHLIB -n hello.c') > > tools::Rcmd('SHLIB hello.c') > > > > What do the commands print? Does the second command fail? > > I basically get no output from the two commands, apart from a new > blank R prompt. So starting a new