similar to: Creating shared object with BASE in EXPORTS on Windows

It looks like `BASE` is a keyword in the .def file specification. https://github.com/bminor/binutils-gdb/blob/master/ld/deffilep.y#L241-L268 For several keywords, I could replicate the syntax error from ld.exe when the keyword was listed in EXPORTS in the .def file. As far as I can tell, the dllname-win.def file is a must in this case making sure none of the keywords get exported there.

I originally posted on this topic on a different thread: https://stat.ethz.ch/pipermail/r-devel/2016-August/072938.html These sources suggested that a safe practice might be to put double quotes around symbol names in EXPORTS in case the symbol name is the same as a linker keyword: - https://sourceware.org/binutils/docs/ld/Symbols.html#Symbols -

On 03/06/2017 6:31 AM, Vivek Sutradhara wrote: > Hi all, > I am having some problems in updating some packages from source. I start > with : > install.packages("Boom",lib="C:/RownLib",type="source") > > I get the following error message : Do you have multiple copies of cygwin1.dll? Duncan Murdoch > > * installing *source* package

On 03/06/2017 7:00 AM, Vivek Sutradhara wrote: > Hi, > As far as I can see, no. > > On checking, I have confirmed that the only location of > cygwin1.dll is : > C:\Rtools\bin I would re-install Rtools, and make sure C:\Rtools\bin appears first in your PATH. Duncan Murdoch > > Thanks > Vivek > > 2017-06-03 12:57 GMT+02:00 Duncan Murdoch <murdoch.duncan at

I am trying to build R under 64bit Windows7. I am using a fresh install of Rtools34 and R-patched_2016-07-05. I am getting the following error: C:/Rtools/mingw_64/bin/gcc -shared -s -static-libgcc -o tcltk.dll tmp.def init.o tcltk.o tcltk_win.o ../../../gnuwin32/dllversion.o -L../../../../Tcl/bin64 -ltc l85 -ltk85 -LC:/R/RLocalSoft/lib/x64 -LC:/R/RLocalSoft/lib -L../../../../bin/x64 -lR

Hi all, I am having some problems in updating some packages from source. I start with : install.packages("Boom",lib="C:/RownLib",type="source") I get the following error message : * installing *source* package 'Boom' ... ** package 'Boom' successfully unpacked and MD5 sums checked ** libs *** arch - i386 c:/Rtools/mingw_32/bin/g++ -std=gnu++11

Hi, As far as I can see, no. On checking, I have confirmed that the only location of cygwin1.dll is : C:\Rtools\bin Thanks Vivek 2017-06-03 12:57 GMT+02:00 Duncan Murdoch <murdoch.duncan at gmail.com>: > On 03/06/2017 6:31 AM, Vivek Sutradhara wrote: > >> Hi all, >> I am having some problems in updating some packages from source. I start >> with : >>

Also note that this can lead to people not being able to load the package if the set of .Call entry points has changed between the old and new versions of the package. We strongly suspect that this is what happened to this Bioconductor user: https://support.bioconductor.org/p/121228/ Note that she's installing the binary and in this case no warning is issued. All we see is: package

On 07/07/2016 5:47 PM, Avraham Adler wrote: > I am trying to build R under 64bit Windows7. I am using a fresh > install of Rtools34 and R-patched_2016-07-05. I am getting the > following error: > > C:/Rtools/mingw_64/bin/gcc -shared -s -static-libgcc -o tcltk.dll tmp.def init.o > tcltk.o tcltk_win.o ../../../gnuwin32/dllversion.o -L../../../../Tcl/bin64 -ltc > l85 -ltk85

thanks for your input Herv?. Glad to hear I'm not the only one still having this issue. In my opinion install.packages should stop with an error (instead of a warning) if this happens. However even if you want to keep the warning, at least make it so that users can set options(warn=2) to get an error if they want one. I tried setting options(warn=2) but for some reason I still get a warning.

Hi Toby, AFAIK it has not been addressed in R. You can handle the problem on your package side, see https://github.com/Rdatatable/data.table/pull/3237 Regards, Jan On Thu, May 30, 2019 at 4:46 AM Toby Hocking <tdhock5 at gmail.com> wrote: > > Hi all, > > I am having an issue related to installing packages on windows with > R-3.6.0. When installing a package that is in use, I

Just noticed that this problem only occurs from within RStudio (v1.1.414). Any ideas why? Am 26.01.2018 um 08:56 schrieb Andreas Kersting: > Hi, > > Installing a source package on Windows using utils::install.packages() > with quiet=TRUE fails, while it works with the default quiet = FALSE. > The problem seems to be caused by the fact that when quiet = TRUE, > stdout and

thanks for the tip Jan. However it would be nice if I didn't have to handle this myself for all of my packages. (and teach my students how to do that) BTW I tried to disable staged installation, and the issue still happens: th798 at cmp2986 MINGW64 ~/projects/max-generalized-auc (master) $ R_INSTALL_STAGED=FALSE R --vanilla -e

Hi, Simon et al.: ????? My attempts to install rJava 0.9-12 from source failed under both macOS 10.15.4 and Windows 10. ????? Below please find what I got just now trying "update.packages()" and selecting "install from sources" on both computers followed by "sessionInfo()" in each case. ????? Thanks for your help. ????? Spencer Graves

Hi all, I am having an issue related to installing packages on windows with R-3.6.0. When installing a package that is in use, I expected R to stop with an error. However I am getting a warning that the DLL copy was not successful, but the overall package installation IS successful. This is quite dangerous because the old DLL and the new R code could be incompatible. I am definitely not the

Thanks a lot for your suggestions. I see what you mean. I have removed all unnecessary files and dependences on https://github.com/Jiefei-Wang/example, but still no luck. I've tried to install the package as a user, not admin, but I got the same error. Also, I apologize for spamming the mail list. I will keep my reply as neat as possible. Martin has suggested checking the encoding of the file

The obvious guess would be that Rstudio is attempting something like redirecting output and getting itself confused. However, it is pretty clearly Their Problem, no? Rstudio has their own support infrastructure. -pd > On 26 Jan 2018, at 09:17 , Andreas Kersting <r-devel at akersting.de> wrote: > > Just noticed that this problem only occurs from within RStudio (v1.1.414). Any

Thanks, Jiefei, unfortunately your example does not work on my system, and also it is far from minimal. The error message you are getting is from Windows and could be caused for example by accidental quoting of the path using single quotes. Issues with RStudio or devtools would have to be discussed in their mailing lists/with their authors, but my guess is that the problem is in your local

Hi, Installing a source package on Windows using utils::install.packages() with quiet=TRUE fails, while it works with the default quiet = FALSE. The problem seems to be caused by the fact that when quiet = TRUE, stdout and stderr are set to FALSE when calling "R CMD INSTALL" with base::system2() here:

On Tue, Feb 13, 2018 at 12:22 PM, Indrajit Sen Gupta <indrajitsg at gmail.com> wrote: > Hi Avraham, > > I tried with the patched version. The same error message. > > gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o > editor.o embeddedR.o extra.o malloc.o opt.o pager.o preferences.o psignal.o > rhome.o rt_complete.o rui.o run.o shext.o