similar to: [LLVMdev] Fwd: Compiling to Win32

Hello, Tom > This tells me that I might have been misunderstood previously, so I am > now clarifying my question: I am asking about compiling to Qin32 WITH > LLVM, not compiling LLVM itself to Win32. So, what dependencies do > programs generated with LLVM need to run on client's Win32 machines? I > hope that this time, my question is more clear. I think answer is also pretty

Hello, Tom > * Intel and AMD machines running on Win32 using MinGW libraries > (native) As you can see here, LLVM is happy on win32. > without installing third-party libraries? Do these libraries need to > be distributed along with the generated executables? It depends on, how exactly you're compiling LLVM. If you'll go with Cygwin-generated binaries, then yes

Could someone running Cygwin or involved in Cygwin help this person please? - Ben ---------- Forwarded message ---------- Date: Thu, 17 Oct 2002 17:58:45 -0400 From: Andrew Greene <agreene at pageflexinc.com> To: openssh at openssh.com Subject: Upgraded to latest cygwin this morning, and ssh refuses to enter binmode. Help! I upgraded to the latest cygwin this morning (not sure when

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

Hello, Something very much resembling a graphical win32-based front-end for rsync is available at http://sync2nas.sourceforge.net It is released under the BSD license for all to enjoy. A few caveats: * It reportedly only works on WinNT/Win2K. Win9x is being looked into at this time. * It is written in Perl/Tk, although all portability conceits were abandoned fairly early on, and it

Hello, Something very much resembling a graphical win32-based front-end for rsync is available at http://sync2nas.sourceforge.net It is released under the BSD license for all to enjoy. A few caveats: * It reportedly only works on WinNT/Win2K. Win9x is being looked into at this time. * It is written in Perl/Tk, although all portability conceits were abandoned fairly early on, and it

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

Hi, all, I'd like to know if there is a way to set the ownership/group/permission when you are transfering files from a Windows clients to a Linux rsync server. I've tried following configurations, and none of them work. rsync -av --owner=test -g MyFolder 192.168.100.1::backup/test rsync -av --owner=500 -g MyFolder --numeric-ids 192.168.100.1::backup/test (500 is numeric id for user

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

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

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 a 32bit version of llvm and use that can my resulting compiler output 64bit binaries?

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

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

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

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

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

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

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 production boxes yet, but it looks promising. From the threads that I have read on the cygwin mailing lists, it would seem that a

> From: Prof Brian Ripley [mailto:ripley@stats.ox.ac.uk] > > The answer seems to be: make sure you are using the tools in a current > tools.zip. Neither Andy nor Uwe were. Both the version of > make.exe and > cygwin1.dll are critical. > > It's also wise to have a fairly recent version of Perl (628 > or later), as > some earlier ones made errors in calls to

Misha Brukman wrote: > I don't know the current status of the LLVA project, so I will let the > current developers chime in. Please send all LLVM and LLVA questions to > llvmdev at cs.uiuc.edu . My apologies for the late reply. > > ----- Forwarded message from N O S P A M <ti_dak at yahoo.com> ----- > > Date: Tue, 17 Jan 2006 09:47:32 -0800 (PST) > From: N O