search for: reimp

Being relatively new to R, I want to use R in connection with a MySQL database. After installing (apparently sucessfully) the package RMySQL (R Version 1.6.2) the result is as follows: > library(RMySQL) > con <- dbConnect(MySQL(), dbname= "test") Error: couldn''t find function "dbConnect" Thank You in advance for help Peter Jörg Peter Baresel Technische

...like systems. Still can't get it to work. Some info below that may indicated where the problem is: * The directory RMySQL\libs is empty---I was not expecting this. * There is a file "README.windows" in RMySQL directory which suggests some changes using the re-import utility "reimp", available at http://mefriss1.swan.ac.uk/~jfonseca/gnu-win32/software/reimp/index.html This file is missing at this location. Instead there is a note stating that it is included in MinGW distribution. I installed this, but did not find this file. * Below is the info from the install...

I have justed upgraded R v1.7.0 on Windows NT 4 and have installed the latest RMySQL (version 0.5-1)and DBI (version 0.1-5) packages. When I issue the following commands (tactfully adjusted) R just crashes and disappears, any ideas? require(RMySQL) m <- dbDriver("MySQL") con <- dbConnect(m, dbname="xxx", user="xxx", password="xxx",

Hi all, I'm looking for a way to install the RMySQL-package into my Windows-version of R (1.8.1). I did successfully install this package into my Linux-version of R (RedHat9), but now I want to do this in my Windows-version too. How to? Regards, Maarten -------------------------------------------------------------- Zie ook/see also: http://www.knmi.nl/maildisclaimer.html

...cause dlltool and ld did not comply with PECOFF Spec. It has some custom formatting and uses the assembler for some reason to generate import libraries, it did not use the short import library format at all. There has been many work arounds for the problem this creates such as the creation of the `reimp` tool. Which imports MSVC built libs creates a def and uses dlltool so that the binutils linker can use it. We should just be using the short import format and the linker should support that. Thus llvm-dlltool was born. Difference from lib =================== Using PE COFF spec (section 8, Impo...

Dear all, In the official document <https://llvm.org/docs/CompileCudaWithLLVM.html>, it is mentioned that CUDA compilation is supported on Windows as of 2017-01-05. I used msys2 to install clang 5.0.1. Then I installed cuda 8.0. However, I basically could not compile any code of cuda by the prescribed setting. I wounder if anyone can successfully compile cuda code by the clang on Windows.

...>> It has some custom formatting and uses the assembler for some reason to >> generate import libraries, it did not use the short import library format >> at all. >> >> There has been many work arounds for the problem this creates such as the >> creation of the `reimp` tool. Which imports MSVC built libs creates a def >> and uses dlltool so that the binutils linker can use it. >> >> We should just be using the short import format and the linker should >> support that. >> Thus llvm-dlltool was born. >> >> >> Differe...

Hi, Linking C++ dynamic libraries has become the bane of my R life. I have a piece of C++ code that I would like to make into a .dll (to call into R). However, this piece of C++ code needs to be linked with a .dll or .lib - which I have been created in Visual C++. Is it possible to link this for use in R? If so, how do I go about doing this is MINGW? I am running R1.9.0 on WinXP. Any

...and uses the assembler for some reason to >>>> generate import libraries, it did not use the short import library format >>>> at all. >>>> >>>> There has been many work arounds for the problem this creates such as >>>> the creation of the `reimp` tool. Which imports MSVC built libs creates a >>>> def and uses dlltool so that the binutils linker can use it. >>>> >>>> We should just be using the short import format and the linker should >>>> support that. >>>> Thus llvm-dlltool was...

...gt;>>>>> to generate import libraries, it did not use the short import library >>>>>> format at all. >>>>>> >>>>>> There has been many work arounds for the problem this creates such as >>>>>> the creation of the `reimp` tool. Which imports MSVC built libs creates a >>>>>> def and uses dlltool so that the binutils linker can use it. >>>>>> >>>>>> We should just be using the short import format and the linker should >>>>>> support that. >&gt...

...ate import libraries, it did not use the short import >>>>>>>> library format at all. >>>>>>>> >>>>>>>> There has been many work arounds for the problem this creates such >>>>>>>> as the creation of the `reimp` tool. Which imports MSVC built libs creates >>>>>>>> a def and uses dlltool so that the binutils linker can use it. >>>>>>>> >>>>>>>> We should just be using the short import format and the linker >>>>>>>&...

...use the short import >>>>>>>>>> library format at all. >>>>>>>>>> >>>>>>>>>> There has been many work arounds for the problem this creates >>>>>>>>>> such as the creation of the `reimp` tool. Which imports MSVC built libs >>>>>>>>>> creates a def and uses dlltool so that the binutils linker can use it. >>>>>>>>>> >>>>>>>>>> We should just be using the short import format and the linker >&...

...y with PECOFF > Spec. > It has some custom formatting and uses the assembler for some reason to > generate import libraries, it did not use the short import library format > at all. > > There has been many work arounds for the problem this creates such as the > creation of the `reimp` tool. Which imports MSVC built libs creates a def > and uses dlltool so that the binutils linker can use it. > > We should just be using the short import format and the linker should > support that. > Thus llvm-dlltool was born. > > > Difference from lib > ==============...

...y with PECOFF > Spec. > It has some custom formatting and uses the assembler for some reason to > generate import libraries, it did not use the short import library format > at all. > > There has been many work arounds for the problem this creates such as the > creation of the `reimp` tool. Which imports MSVC built libs creates a def > and uses dlltool so that the binutils linker can use it. > > We should just be using the short import format and the linker should > support that. > Thus llvm-dlltool was born. > > > Difference from lib > ==============...

...y with PECOFF > Spec. > It has some custom formatting and uses the assembler for some reason to > generate import libraries, it did not use the short import library format > at all. > > There has been many work arounds for the problem this creates such as the > creation of the `reimp` tool. Which imports MSVC built libs creates a def > and uses dlltool so that the binutils linker can use it. > > We should just be using the short import format and the linker should > support that. > Thus llvm-dlltool was born. > > > Difference from lib > ==============...

...Serious Sam II demo installer creates blank window 9714 MapViewOfFile with write permissions should not succeed on a read-only file mapping 9715 winecfg should allow display resolution beyond 120dpi 10129 Guitar Rig 3 crashes 10375 Stranger demo makes Wine segfaults 10579 mingw32: reimp and other tools can't launch each other 10727 .Net 2.0 does not install 10810 Constant crash while using EDXOR 10859 access violation in mshtml.dll since 0.9.48 / Heredis 9 10980 ConvertImage cannot run 11092 cutscene does not display correctly - jedi knight dark forces II demo...