search for: binpref

On Tue, Feb 13, 2018 at 2:20 AM, Jeroen Ooms <jeroenooms at gmail.com> wrote: > Thanks for your question. Your logs show that 'gcc' is not found. As > of R 3.3 you need to set the path to the compiler using the BINPREF > variable. This is because we ship two separate versions of gcc, one > targeting win32 and one targeting win64. I am not sure what your > rtools installation looks like, but could you try setting this > environment variable: > > BINPREF="M:/R/Rtools-3.4/mingw_$(WIN)/bin/&q...

...elder <peter.langfelder at gmail.com> wrote: > On Tue, Feb 13, 2018 at 2:20 AM, Jeroen Ooms <jeroenooms at gmail.com> wrote: > >> Thanks for your question. Your logs show that 'gcc' is not found. As >> of R 3.3 you need to set the path to the compiler using the BINPREF >> variable. This is because we ship two separate versions of gcc, one >> targeting win32 and one targeting win64. I am not sure what your >> rtools installation looks like, but could you try setting this >> environment variable: >> >> BINPREF="M:/R/Rtools...

Good evening. Testing the most recent version of Rtools, the build stops about when text.c is being compiled in the tools package (just after R.Lapack). The compilation is looking for gcc in C:, even though RTOOLS is set for another drive, and the compilation has successfully run until this point. This did not happen last night with version 1955. I've uninstalled and reinstalled Rtools three

...e who worked on this. Is there a way to > > tell which toolchain built a given R-devel binary? > > If not, can you let us know when there is one on CRAN that was > > built with the new Rtools? > > If you look in etc/*/Makeconf, you'll see something like this: > > BINPREF ?= $(RTOOLS)gcc492_64/bin/ > > hopefully from tomorrow onwards. If today's build was with the new > toolchain, you should see a hardcoded path to where I have Rtools > installed on the build machine, which isn't so helpful. The previous > toolchain left BINPREF blank. >...

Hi all, I'm trying to set up the Windows Rtools toolset for building packages with compiled code. I installed for Windows R-3.4.3 from CRAN and installed Rtools-3.4 in a custom location M:\R\R-3.4.3 and M:\R\Rtools-3.4 Following the instructions, in shell, I set Path=M:\R\Rtools-3.4\bin;M:\R\Rtools-3.4\gcc-4.6.3\bin;M:\R\R-3.4.3\bin;... (the ... are other paths irrelevant for R/Rtools).

...tell which toolchain built a given R-devel binary? > >>> If not, can you let us know when there is one on CRAN that was > >>> built with the new Rtools? > >> > >> If you look in etc/*/Makeconf, you'll see something like this: > >> > >> BINPREF ?= $(RTOOLS)gcc492_64/bin/ > >> > >> hopefully from tomorrow onwards. If today's build was with the new > >> toolchain, you should see a hardcoded path to where I have Rtools > >> installed on the build machine, which isn't so helpful. The previous >...

...ly. It is strange that you did not get the attachments. I am pasting the contents of the MkRules.local here: ------------------------------------------------------------------- #-*- Makefile -*- ## This is only used when building R itself but it does customize ## etc/*/Makeconf using LOCAL_SOFT, BINPREF[64], IMPLIB and R_ARCH ## Customize by copying to MkRules.local and uncommenting and editing ## some of the definitions there. ## ## =========== configuration macros for building packages ================ # Absolute path to '/usr/local' software collection. The versions used # on CRAN ca...

----- Original Message ----- > From: "Duncan Murdoch" <murdoch.duncan at gmail.com> > To: "Hsiu-Khuern Tang" <tangoh at gmail.com>, r-devel at r-project.org > Sent: Monday, March 9, 2015 10:40:02 AM > Subject: Re: [Rd] Notes on building a gcc toolchain for Rtools (but not multilib) > > On 09/03/2015 11:07 AM, Hsiu-Khuern Tang wrote: > > On

...> > > > Thanks to you and everyone who worked on this. Is there a way to tell which toolchain built a given R-devel binary? > If not, can you let us know when there is one on CRAN that was built with the new Rtools? If you look in etc/*/Makeconf, you'll see something like this: BINPREF ?= $(RTOOLS)gcc492_64/bin/ hopefully from tomorrow onwards. If today's build was with the new toolchain, you should see a hardcoded path to where I have Rtools installed on the build machine, which isn't so helpful. The previous toolchain left BINPREF blank. If you want to use your o...

...uctions, in shell, I set > Path=M:\R\Rtools-3.4\bin;M:\R\Rtools-3.4\gcc-4.6.3\bin;M:\R\R-3.4.3\bin;... > (the ... are other paths irrelevant for R/Rtools). Thanks for your question. Your logs show that 'gcc' is not found. As of R 3.3 you need to set the path to the compiler using the BINPREF variable. This is because we ship two separate versions of gcc, one targeting win32 and one targeting win64. I am not sure what your rtools installation looks like, but could you try setting this environment variable: BINPREF="M:/R/Rtools-3.4/mingw_$(WIN)/bin/" I think this will do th...

...t the attachments. I am > pasting the contents of the MkRules.local here: > > ------------------------------------------------------------------- > > #-*- Makefile -*- > > ## This is only used when building R itself but it does customize > ## etc/*/Makeconf using LOCAL_SOFT, BINPREF[64], IMPLIB and R_ARCH > > ## Customize by copying to MkRules.local and uncommenting and editing > ## some of the definitions there. > ## > > ## =========== configuration macros for building packages ================ > # Absolute path to '/usr/local' software collection...

Hello: I'm trying to use Rcmd SHLIB to compile a single file, sann.c, to get sann.dll. I was able to get make libR.a to work, after going into MkRules and changing the line DLLTOOL=$(BINPREF)dlltool -k --as $(AS) to read DLLTOOL=C:/MINGW-1.1/bin/dlltool -k --as $(AS) But now I get: C:\rw1051\src\gnuwin32>Rcmd SHLIB sann.c make: make: Command not found make: *** [libR] Error 127 My path is as follows: C:\rw1051\src\gnuwin32>path PATH="C:\Rtools\";C:\Mingw-1.1\bin;...

...s there a way to >>> tell which toolchain built a given R-devel binary? >>> If not, can you let us know when there is one on CRAN that was >>> built with the new Rtools? >> >> If you look in etc/*/Makeconf, you'll see something like this: >> >> BINPREF ?= $(RTOOLS)gcc492_64/bin/ >> >> hopefully from tomorrow onwards. If today's build was with the new >> toolchain, you should see a hardcoded path to where I have Rtools >> installed on the build machine, which isn't so helpful. The previous >> toolchain left...

Hi All, I am trying to compile R from source on a 64 bit Windows. I have downloaded and installed all the third party software as per the R - documentation. The compilation starts fine and after a while it stops with the following error message: D:/Rtools/mingw_64/bin/../lib/gcc/x86_64-w64-mingw32/4.9.3/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lRgraphapp collect2.exe: error: ld

...n (JRC-ISPRA) Cc: r-devel Subject: Re: [Rd] Problem with R_registerRoutines On Windows this warning may be a false positive if R cannot find "objdump.exe" which is required for this check. I think this is actually a bug in R because it should be looking for "objdump.exe" inside BINPREF (where gcc is) rather than on the PATH. Can you check if you get the same warning if you upload the package to https://win-builder.r-project.org ? On Fri, Feb 23, 2018 at 10:28 AM, <Jon.SKOIEN at ec.europa.eu> wrote: > Dear list, > > I am trying to update a package to pass th...

...iven R-devel binary? > > >>> If not, can you let us know when there is one on CRAN that was > > >>> built with the new Rtools? > > >> > > >> If you look in etc/*/Makeconf, you'll see something like this: > > >> > > >> BINPREF ?= $(RTOOLS)gcc492_64/bin/ > > >> > > >> hopefully from tomorrow onwards. If today's build was with the > > >> new > > >> toolchain, you should see a hardcoded path to where I have > > >> Rtools > > >> installed on the bui...

...E/src/gnuwin32/bitmap folder but when I tried the ./configure command I got an error again (I'm not an expert user, still learning). My MkRules.local file is the following: #-*- Makefile -*- ## This is only used when building R itself but it does customize ## etc/*/Makeconf using LOCAL_SOFT, BINPREF[64], IMPLIB and R_ARCH ## =========== configuration macros for building packages ================ # Absolute path to '/usr/local' software collection. The versions used # on CRAN can be found under http://www.stats.ox.ac.uk/pub/Rtools/goodies LOCAL_SOFT = ## ============== configuration...

Dear list, I am trying to update a package to pass the CRAN-checks. But I am struggling with the following note: File 'psgp/libs/i386/psgp.dll': Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' File 'psgp/libs/x64/psgp.dll': Found no calls to: 'R_registerRoutines', 'R_useDynamicSymbols' It is good practice to register native

...> >>> If not, can you let us know when there is one on CRAN that was > > > >>> built with the new Rtools? > > > >> > > > >> If you look in etc/*/Makeconf, you'll see something like this: > > > >> > > > >> BINPREF ?= $(RTOOLS)gcc492_64/bin/ > > > >> > > > >> hopefully from tomorrow onwards. If today's build was with the > > > >> new > > > >> toolchain, you should see a hardcoded path to where I have > > > >> Rtools > > >...

On Windows this warning may be a false positive if R cannot find "objdump.exe" which is required for this check. I think this is actually a bug in R because it should be looking for "objdump.exe" inside BINPREF (where gcc is) rather than on the PATH. Can you check if you get the same warning if you upload the package to https://win-builder.r-project.org ? On Fri, Feb 23, 2018 at 10:28 AM, <Jon.SKOIEN at ec.europa.eu> wrote: > Dear list, > > I am trying to update a package to pass th...