similar to: [LLVMdev] llvm 32bit with 64bit output?

2012/12/21 Flexicat01 <nekroze.lives at gmail.com>: > I am looking at starting a project to make a toy language that is targeted > purely at 64bit windows. I have never used llvm or anything like it i am > just trying to learn new things. > > However there are several problems, as far as i have seen, with compiling > llvm in 64bit on windows. So i was wondering if i compile

You can generate 64-bit binaries with a 32-bit LLVM without any issue. The target machine in your case may differ from the "host target", but it shouldn't be any problem. I have managed to compile LLVM on Windows using the compiler from Windows 7 SDK (and CMake). I don't remember what runtime binaries it required, but I guess it was the regular MSVC runtime. -Krzysztof --

At the moment i have set up cygwin using its llvm package to learn with and, as i prefer developing in that unix style environment and using the command line i will stick with that for a bit. Since you say a 32bit llvm can generate 64bit binaries i also assume that they shouldnt require the cygwin runtime (cygwin1.dll) but if it does i could at that point switch to mingw with cygwin hopefully or

I did try the cygwin mingw-x86_64 but i couldn't get llvm to compile, but i did try and compile clang and compiler_rt as well, may have to try again soon. On windows i'm not interesting in i686 or any 32 bit compiling just 64 bit alone but i don't need a jit anyways for my language. If i use the cygwin environment to build llvm do i have to use cmake or can i use the standard

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 : >>

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

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

David Starks-Browning [starksb@ebi.ac.uk] writes: > Are you also distributing the source to cygwin1.dll? It is illegal > not to. Well, if it's an unmodified version, I expect a simple pointer to the Cygwin site and/or CVS tree would be sufficient. Physical distribution is not necessarily the only way to satisfy the GPL, and if the included cygwin1.dll is simply a binary downloaded

This question is perhaps one you have seen before but I have not found an answer to as yet. Rsync uses cygwin1.dll as does openssh. Is there a more current compilation of openssh that uses a more current cygwin1.dll such that both rsync and openssh can function on the same version? This is important because of improvements made to cygwin1 that affect rsync speed. Thanks for your thoughts and

On 12/20/2012 7:48 PM, Krzysztof Parzyszek wrote: > > LLVM will only generate object files. You will need to link them to get > the final executable. This will determine whether (and if) you need any > special DLLs. Correction: linking will associate your executable with specific libraries. Whether you need them or not will depend on the features that your language provides.

https://bugzilla.samba.org/show_bug.cgi?id=2328 ------- Additional Comments From service@redterra.net 2005-04-13 06:45 ------- The legendary cygwin/rsync/ssh hang problem. I have been tracking this for a while now and can say that the latest cygwin install appears to have fixed the problem on one of the setups that has consistantly failed in the past. Have not put the update on to any

I'm trying to use rsync under Cygwin on 2 machines running Windows 2000 Server There's a 2MB link between them and I'm using SSH setup for a passwordless connection rsync hangs part way through transfers and when run again hangs at the same place in the same files with no explanation no matter what verbosity level I set it to. Each time it hangs it leaves an rsync process running on

Hi there! I'm building a VB.NET application in order to setup the configuration files of a net (and this is the really easy part of my project) via INI file, but now I've got some problems... launching tincd -n [NET] -K I should insert some variables, and it is impossible to auto-fill them. So I've downloaded the source files and opened it. I found the part of that code and

Hello! I have just read mails in thread <http://tolstoy.newcastle.edu.au/R/devel/04a/0583.html> about problems with Cygwin and Rtools. I had the same problems and kept just the newest cygwin1.dll and things seem OK now. However I currently hit the problem with Perl (I have ActiveState and Cygwin Perl installed). When I tried to work with 'Rdconv' in Cygwin I get the following: $

Hi, I installed the rsync on windows 2000 server which is synchronized folders with NT4 across the seas. from the NT4 to Windows 2000 the process is working fine, but trying to pull the opposite I get error messages like : "failed to connect to <server ip> - Connection refused" , and telnet to port 873 gives the error message: "Could not open a connection to host on port 873

I've been attempting to create a new R package and recently removed the cygwin installation from my machine since R requires the use of the MingW tools for building an R package with C code. However, when I tried to build a source package, I found the following results: * removing junk files * building 'Rconifers_0.7-1.tar.gz' tar:

OK, I set up a new PC with a fresh XP load to be my rsync server. Rsync by itself seems to work fine (thank God. I'm going nuts.) I am still having problems when I throw ssh into the mix. At least now, things don't crash, but they do hang. The file list gets build, the transfer starts and it gets through maybe a few hundred files, but then everything stops. All the processes are still

This is the first time I've ever compiled from sources so bear with me. OS: Windows 2000 PATH: .: D:/Rtools/: D:/mingw/bin/: C:/Progra~1/Perl/bin: D:/texmf/miktex/bin/: D:/Progra~1/HTMLHe~1: D:/Progra~1/R/rw1062/bin/: C:/Progra~1/Insightful/splus61/cmd/: D:/cygwin/bin: D:/Progra~1/SSHCom~1/SSHSec~1: D:/Progra~1/Tcl/bin/: C:/Progra~1/Microso~3/VC98/Bin

I need to distribute rsync (useable for both client and --daemon) on Win32. Distributing cygwin1.dll is, well you know, a bad idea. I took a shot at building under MingW but ran into an ugly looking error: > checking for socklen_t... no > checking for socklen_t equivalent... configure: error: Cannot find a > type to use in place of socklen_t I will pay $50 for a MingW build of latest