search for: toolsets

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

...this: >> >> <Project >> xmlns="http://schemas.microsoft.com/developer/msbuild/2003" >> <http://schemas.microsoft.com/developer/msbuild/2003>> >> <Import >> Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props"Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props')"/> >> <Import >> Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\...

Hi Hans, I think installer.bat found my visual Studio installation because it installed the Win32 toolsets but not the x64 ones. (It took me a while to work this out ;-) I installed the x64 toolsets by hand and they seem to work. I think the installer ran as administrator. I explicitly ran it that way again (asking it to uninstall first) just to be sure. It didn't seem to make any difference. I...

...; wrote: > I changed tooset-vs2013.props to this: > > <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" > <http://schemas.microsoft.com/developer/msbuild/2003>> > <Import > Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props" > Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props')"/> > <Import > Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Tools...

...ng 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 now when I try to compile a file, I > get an error message saying that the build tools for llvm-2013 cannot be > found. I guess that this is because the installer didn't correctly add the > LLVM tools to $PATH. How can I correctly add the LLVM tools to the path? > > R...

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,

...6. > > > > So, hopefully very soon we will have all the required kits to build > > firefox for CentOS-7 .. CentOS-6 may be a bit longer. > > > > Status currently is that I have a version built for CentOS-7 x86_64. > > I am currently still building the require toolsets for i386 as > firefox.i686 is released as a multilib package in the x86_64 repo. > > So, I can't release the x86_64 package without the i686 one. > > You can download the x86_64 package manually if you don't want to wait > .. but I should have them both (i686 and x86_64)...

...ly very soon we will have all the required kits to build >>>> firefox for CentOS-7 .. CentOS-6 may be a bit longer. >>>> >> >>> Status currently is that I have a version built for CentOS-7 x86_64. >> >>> I am currently still building the require toolsets for i386 as >>> firefox.i686 is released as a multilib package in the x86_64 repo. >> >>> So, I can't release the x86_64 package without the i686 one. >> >>> You can download the x86_64 package manually if you don't want to wait >>> .. but I s...

...ns, Answers inline below. Regards, Eric On 9/30/14, 8:05 AM, Hans Wennborg wrote: > On Mon, Sep 29, 2014 at 7:56 PM, Eric Mader <emader at gmx.us> wrote: >> Hi Hans, >> >> I think installer.bat found my visual Studio installation because it >> installed the Win32 toolsets but not the x64 ones. (It took me a while to >> work this out ;-) I installed the x64 toolsets by hand and they seem to >> work. > Hmm, that's interesting. Is your x64 toolset path different besides > substituting the Win32 dir with x64? They're the same except for Win32 /...

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

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

Hi all, I could find the 1.1 and 2 repos gently provided by Tru Huynh, but quid of a v3 of the toolset? I've just found that Qt 5.4 requires what's shipped in this v3 (gcc 4.9.1, binutils 2.24) and would prefer installing those from a repo. If not, the sources will rule. Any hint? Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name:

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

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

Hi, I have a machine with a Debian Stable installation that runs OpenVSwitch to connect a virtual machine on the same box. The machine is also running shorewall. The problem that I''m having is that shorewall try to run before openvswitch, this makes that shorewall fails because it can''t determine the IP of the virtual interface generated by openvswitch that start after

I am pleased to announce the immediate availability of Developer Toolset 3 on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-3-toolchain $ scl enable

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

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

I am pleased to announce the immediate availability of Developer Toolset 4 on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-4-toolchain $ scl enable

I am pleased to announce the immediate availability of Developer Toolset 3 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install devtoolset-3-toolchain $ scl