similar to: Watch out for the latest Cygwin upgrade

Your install dir has a whitespace. Have you tried quoting? e.g. <LLVMInstallDir>"C:\Program Files (x86)\LLVM"</LLVMInstallDir> Best regards, Rafael Auler On Mon, Sep 29, 2014 at 7:38 PM, Eric Mader <emader at gmx.us> wrote: > I changed tooset-vs2013.props to this: > > <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" >

I replaced all instances of "$(Platform)" with "x64" for the x64 .props file and it still fails, so it looks like that guess was wrong as well. Regards, Eric On 9/29/14, 2:11 PM, Eric Mader wrote: > Quoting doesn't seem to make a difference. Strangely, the Win32 > toolset seems to work. (Where "work" means that clang runs and > produces a bunch of

Open the file toolset-vs2013.props and you'll understand what's happening and where the path is set. It tries to fetch the LLVM installation path from the Windows registry. Just fix this (maybe editing your registry or editing the .props file, whatever suits you best). On Mon, Sep 29, 2014 at 5:33 PM, Eric Mader <emader at gmx.us> wrote: > I copied the x64 toolsets by hand and

I tried ot build rpvm in my own makefile. But runs into some linker errors like e.g. undefined reference to `_R_alloc' My enviornment looks like this: CYGWIN pvm 3.4 compiled under cygwin myself R installed from the rw2001.exe setup file. I guess that the R under rw2001.exe was build with some other compiler? I then tried to compile R myself under CYGWIN but runs into the following

I was hoping to not have to build LLVM myself, especially on Windows. Can anybody help me with the Windows installer? Failing that, I find the directions for how to compile on Windows hard to follow? Can I build using Cygwin? Regards, Eric On 9/29/14, 8:11 AM, Rafael Auler wrote: > I'm not sure about the Windows installer, but if you build and install > LLVM for Windows from the

I'm trying to write an automatic check of the toolset installation for R. It'll get all the tools to print their version numbers, and complain if they aren't acceptable ones. However, I can't see how to get sh to print version information. Is there some way to do it? The sh I'm worried about is the one that comes with Cygwin, if there isn't a standard approach. Duncan

I’m trying to install LLVM-3.6.0-r218288-win32.exe on Windows 7 Ultimate x64. The install doesn’t complain, but the toolset doesn’t show up in either Visual Studio 2013 or Visual Studio 2010. Also I selected the choices to add LLVM to the path for every user and put an LLVM icon on the desktop. Neither of this happened. Can anyone tell me how to get this to work? Regards, Eric Mader

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 2018-07-05 at 06:16 -0500, Johnny Hughes wrote: > On 07/03/2018 09:04 AM, Sean wrote: > > > <snip> > OK guys .. Firefox 60 is going to take some time .. likely more for > CentOS-6 than CentOS-7. > > They both (C6 and C7 versions) require many non OS tools to build. > > For CentOS-7 .. we need the

On 07/11/2018 01:36 PM, Johnny Hughes wrote: > On 07/11/2018 08:28 AM, Phil Wyett wrote: >> On Wed, 2018-07-11 at 06:31 -0500, Johnny Hughes wrote: >>> On 07/09/2018 09:38 AM, Johnny Hughes wrote: >>>> On 07/06/2018 10:30 AM, Johnny Hughes wrote: >>>>> On 07/05/2018 02:27 PM, Phil Wyett wrote: >>>>>> On Thu, 2018-07-05 at 06:16 -0500,

I saw an article this morning about the RH developer toolset. basically it includes a couple of packages like PHP python mysql (etc) that are later packages than that included in the released version like a 6.4 for example. So instead of php 5.3 with patches it would be php 5.4 and so on. That is great for a couple packages - but what about more up to date libraries like glib. 6.4 is way behind

On Wednesday 20 October 2004 12:01, Reid Spencer wrote: > I'm re-thinking my penchant for automake. automake is great for many > standard applications that just need to get portable makefiles up and > running quickly. However, it turns out that LLVM is "different enough" > from a standard application that automake might not be the best choice. I might just here to

On 07/06/2018 10:30 AM, Johnny Hughes wrote: > On 07/05/2018 02:27 PM, Phil Wyett wrote: >> On Thu, 2018-07-05 at 06:16 -0500, Johnny Hughes wrote: >>> On 07/03/2018 09:04 AM, Sean wrote: >>>> >> >> >> <snip> >> >>> OK guys .. Firefox 60 is going to take some time .. likely more for >>> CentOS-6 than CentOS-7. >>

On 07/11/2018 09:20 AM, Leonard den Ottolander wrote: > On Thu, 2018-07-05 at 06:34 -0500, Johnny Hughes wrote: >> I pushed the 3 SRPMs that are not in CR to: >> >> http://vault.centos.org/6.10/os/Source/SPackages/ > >> All the other new SRPMS should be available from : >> >> http://vault.centos.org/6.9/cr/Source/SPackages/ > > When you have time,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 2018-07-11 at 06:31 -0500, Johnny Hughes wrote: > On 07/09/2018 09:38 AM, Johnny Hughes wrote: > > On 07/06/2018 10:30 AM, Johnny Hughes wrote: > > > On 07/05/2018 02:27 PM, Phil Wyett wrote: > > > > On Thu, 2018-07-05 at 06:16 -0500, Johnny Hughes wrote: > > > > > On 07/03/2018 09:04 AM, Sean

Hi. Just now when I tried to compile a .cpp file using the LLVM toolset in VS2019, I got two error messages from lld-link: " lld-link : error : Debug\cust_std_lib_facilities.obj: unknown file type lld-link : error : Debug\Ex10_10.obj: unknown file type " What's the reason for this, and is there a way to fix it? This is the first time I'm saying this error; I've used LLVM

On Thursday 21 October 2004 01:54, Vladimir Prus wrote: > On Wednesday 20 October 2004 12:01, Reid Spencer wrote: > > I'm re-thinking my penchant for automake. automake is great for many > > standard applications that just need to get portable makefiles up and > > running quickly. However, it turns out that LLVM is "different enough" > > from a standard

Hi, May be it's not clear to everyone.. so this's just a quick notice to everyone. Don't use CentOS 7 as a developer workstation since currently there is not included any developer IDE. As eclipse was pulled out from the main distro and put into Red Hat Developer Toolset (which is imho a good idea not to use a 7 years old IDE). But Red Hat Developer Toolset is still not supported on

Recently I have heard reports like the one below a couple of times: Tineke Casneuf wrote: > However I did encouter an error when trying to install a self-made dummy > package. I am sure it is not due to the package because it can be build on > someone else's windows PC. > > The error message is *rm: failed to get attributes of `/': No such file or > directory. Today I

Hola, me llamo Ángel y estoy haciendo una aplicación en Java que usa funciones ya implementadas en R, siento molestarte para esta tontería, pero es que ya ni paso de la instalación del JRI. A ver si me puedes ayudar, te lo agradecería muchísimo!! A ver, yo leí en la página de JRI que hacen falta las mismas herramientas que para R, MINGc y el conjunto de herramientas de /bin (/bin toolset), vale,

Hi folks, I took the plunge recently to move NAT from my router to my shorewall config, and mostly things are ok. Most traffic moves around without problems but sometimes I am having trouble accessing external webservers from non-gateway internal computers. I have stared at the traffic in wireshark (even 2 wiresharks on different interfaces) but can''t see the problem. Nevertheless