similar to: I have finished compiling of R 64 bit on 64 bit Windows use MINGW64

Dear all: Now RGui on windows no HighDPI awareness.try add HighDPI awareness to RGui in last two days. I write an initial POC(just for verify and only SystemDPI awareness partial implemented) , try to mod graphapp used in R to implemented DPI scaling. it seems works on my laptop , but need further test. So I post the patch https://github.com/armgong/misc-r-patch/blob/main/dpi-c-code.diff

there is my code,  expect return value  is a data frame but R say it is list: SEXP Julia_R_MD_NA_DataFrame(jl_value_t* Var) {  SEXP ans,names,rownames;  char evalcmd[4096];  int i;  const char* dfname="DataFrameName0tmp";  jl_set_global(jl_main_module, jl_symbol(dfname), (jl_value_t*)Var);  //Get Frame cols   sprintf(evalcmd,"size(%s,2)",dfname);  jl_value_t*

hello everyone,recently I write a package for R call Julia through Julia C API https://github.com/armgong/RJulia now the package can do 1 finish basic typemapping, now int boolean double R vector to julia 1d-array is ok,and julia int32 int64 float64 bool 1D array to R vector is also ok. 2 R STRSXP to julia string 1D array and Julia string array to STRSXP is written but not sure it is correct or

recently I used gcc 4.9.1 (http://sourceforge.net/projects/mingw-w64/files/Toolchains targetting Win64/Personal Builds/mingw-builds/)on windows to build R,but failed when link R.dll ,it report linker status 5.  after some digging, I found when use gcc 4.9.1 64 bit on windows there are lots of .refptr.*(* is r function name) in R.def, which lead build fail.so I add a simple path to

hello everyone: On this boring weekend, I tried compile R-trunk on windows 11 arm64 using clangarm64+msys2 on macbook m1 , it surprisingly easy to compiled and run. more investigation and test and code modify need to be done ,but IMO this is a good beginning !! to compile R on windows 11 arm64 just need : 1 svn checkout R-trunk and add USE_LLVM=YES in MKRules.dist or Mkrules.local 2 install

Hi, I tried to do a build with CMake, Ninja, and MinGW32 and MinG64 respectively: MinGW32 failed on an missing sys/mman.h (POSIX-specific header): D:/test/llvm-trunk/projects/compiler-rt/lib/enable_execute_stack.c:13:22: fatal error: sys/mman.h: No such file or directory #include <sys/mman.h> ^ MinGW64 failed on an #error directive:

I'm trying to follow the example in the R for Windows FAQ on running gdb and am getting stuck because gdb tells me "Cannot access memory at address ...". Here's what my gdb session looks like (This one from a cygwin shell, but same results from plain Windows CMD shell): $ cd R-devel/src/gnuwin32 $ gdb ../../bin/Rgui.exe GNU gdb 5.2.1 Copyright 2002 Free Software Foundation,

Chen, see http://llvm.org/docs/GettingStarted.html#pf_12 ...Takumi ps. Excuse me, PE+ (aka pep) means "Executable file format for WIndows x64". 2011/5/16 陈晓宇 <xychen0921 at gmail.com>: > The stack trace: > > Starting program: > C:\MinGW\msys\1.0\home\xchen\llvm-obj\lib\Target\CellSPU/../.. > /../Debug/bin/tblgen.exe -I

I was building llvm2.9 using MinGW64 on windows, msys was 32 bit so I specified --host option for a cross compiling. Following are my configure options: ../llvm2.9/configure --prefix=/home/AutoESL/llvm-obj --host=x86_64-w64-mingw32 --disable-multilib The error: make[1]: Entering directory `/home/AutoESL/llvm-obj/lib/VMCore' make[1]: ***

I'm trying to build the 1.4.0 development version of R for Windows. I'll be posting problems as they arise, until I give up (or succeed), or someone asks me to stop. 1. I don't have zlib, the compression library. The source file gnuwin32/unzip/WHERE says to get it from ftp://ftp.info-zip.org/pub/infozip/zlib/zlib.html; that web site says it has been closed and redirects me to

Guys, you can exclude me (dyatkovskiy) from this list, since I reverted my changes in r162354. -Stepan. llvm.buildmaster at lab.llvm.org wrote: > The Buildbot has detected a new failure on builder clang-native-mingw64-win7 while building cfe. > Full details are available at: > http://lab.llvm.org:8011/builders/clang-native-mingw64-win7/builds/876 > > Buildbot URL:

Hi, Trying to build llvm.dll (8.0.0) with mingw64 (gcc 8.1.0) using cmake. After linking for hours and consuming some 7GB of RAM, ld.exe finally bails out with: X:/tools/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/8.1.0/../../../../x86_64-w64-mingw32/bin/ld.exe: Error: export ordinal too large: 283482 The command I used is: cmake \ -DLLVM_TARGETS_TO_BUILD=X86 \ -DCMAKE_BUILD_TYPE=Debug \

Hi, I just did a "make install" on Win7x64 using Mingw64 and it dropped off the files in "C:\Program Files (x86)\LLVM". That's almost right, but nicer would be if the 64-bit build was dropped off in "C:\Program Files\LLVM". I am fairly confident that it is me who is doing something wrong because I simply do this: (retrieve trunk version of LLVM, Clang,

git://git.zytor.com/users/genec/syslinux.git Branch win64-mingw32-ubuntu-for-hpa This adds the compiler prefix used in Debian/Ubuntu to the list (amd64-mingw32msvc-). Too bad /bin/sh doesn't support brace expansion. -- -Gene

Chen, 2011/5/13 陈晓宇 <xychen0921 at gmail.com>: > ../llvm2.9/configure --prefix=/home/AutoESL/llvm-obj >                             --host=x86_64-w64-mingw32 >                             --disable-multilib Please try with "--build=x86_64-w64-mingw32", not "--host". If you would still have any troubles, make sure your x86_64-w64-g++.exe can generate correct

I have successfully installed the cross compiled dll's and other files supplied by centos 7 on a machine running Windows 7. When I run GtkLauncher.exe it comes up with the google page displayed. However, when I try to view "http://www.msnbc.com" Gtklauncher crashes in libjavascriptcore.dll at offset 0xa4944. nfl.com comes up, but then crashes in the same place. My questions

Hello First of all, note the "llvm" in the mailing list title. Clang questions should be asked in other ML. > 3. Run cmake and let it figure out that its using Clang on Windows. > 4. Build and realize that the link doesn't work because CMake pulls in the > wrong libraries (per default it uses Microsoft naming conventions: foo.lib > instead of libfoo.a). It seems like

Hi, there, I have 2 machines ( running Linux Red Hat 8.0 and Windows Xp individually), which share a broadband Internet connection through a router. After installing Samba 2.2.7.a on Linux machine, I can use "smbclient" to access Windows machines, see the files and transfer files. Linux machine info: name: WINNY share folder name: gong ip: 192.168.123.153 valid

clang is compiler http://clang.llvm.org, it is fast and better c compiler then gcc, yesterday i use clang and gfortran compile R. The only two change in source code is : 1. the configure file (in confiure when test include wctype.h,gcc can compile but clang need include both wchar.h wctype.h),so this is patch --- /r/configure +++ /myr/configure @@ -39172,6 +39172,7 @@ cat

Hi again, I am regularly building my small STL-enabled C++ project using Mingw64 on Windows x64 and the program runs fine (it builds and runs fine on x64 Linux too). Then I got brave and decided to try out Clang, because I'd eventually like to take a look at the quality of the generated code, and then did the following: 1. Set CC to clang. 2. Set CXX to clang++. 3. Run cmake and let it