similar to: Noise Ninja 2.10 vs. wine-0.9

It's been a while since I used LTSpice, but it always worked on Wine no matter which distro I was running. However, I recently installed it on both Mint 11 and Mint 12 and had the same problems. The first problem I noticed was when I installed it, it placed the desktop configuration file on my Mint desktop. I had never seen that happen before. The second problem was that the application

My sincere recognition for the great work developed when making Wine. I am having a problem with the version 1.2-rc3; specifically I cannot write (from applications that they run in Wine), toward NTFS partitions; the strange thing is that I can read and until erasing files (from the browser of Wine or from Xplorer2 for example). If I run Ltspice for example, I can load without problems the

The Wine development release 4.0-rc5 is now available. What's new in this release (see below for details): - Bug fixes only, we are in code freeze. The source is available from the following locations: https://dl.winehq.org/wine/source/4.0/wine-4.0-rc5.tar.xz http://mirrors.ibiblio.org/wine/source/4.0/wine-4.0-rc5.tar.xz Binary packages for various distributions will be available

Hi, I am a Mac osx 10.6 user. I followed this tutorial (http://web.engr.oregonstate.edu/~traylor/ece391/install_ltspice) to install wine and LTspice. After download the LTspiceIV.exe from Linear website. I put it into my home folder, and try to run "wine LTspiceIV.exe" from my terminal. Here is the error message I got: err:module:map_image Could not map section .rdata, file probably

I just installed some enhancements with winetricks. One or more of the components I installed broke how my WINE works. The problem is most evident in the toolbar icons and I think it's related to transparency. The background of the toolbar icons in LTSpice are now black. Many of the icon images are drawn with dark lines making them unreadable. Several applications now behave this way

The Wine development release 4.0-rc6 is now available. What's new in this release (see below for details): - Bug fixes only, we are in code freeze. The source is available from the following locations: https://dl.winehq.org/wine/source/4.0/wine-4.0-rc6.tar.xz http://mirrors.ibiblio.org/wine/source/4.0/wine-4.0-rc6.tar.xz Binary packages for various distributions will be available

The Wine development release 5.5 is now available. What's new in this release (see below for details): - Builtin libraries use the new UCRTBase C runtime. - Compatibility mode used when reporting Windows version. - Better support for debug information in PE files. - Support for linguistic case mappings. - More attributes supported in WebServices. - Various bug fixes. The source

Building LLVM with Visual Studio is a bit of a pain because the available methods are slow and doesn't make good use of multiprocessor systems. >From now on it is possible to build LLVM+Clang with the usual cmake method but using Ninja, an ultra-fast tool that knows how to take advantage of the availabe execution threads. Ultra-fast is no exageration: with a warm cache, a no-op build of

On Jun 17, 2012, at 7:23 PM, Óscar Fuentes wrote: > OTOH it's my personal > opinion that you may be explaining too much: it is not necessary to > explain, nor even mention, the different available build tools on > Windows. As LLVM and Clang are developer tools, one can suppose that > the > user knows how to run a build. IMO, Mikael's efforts are on-target and very

On Sun, Jun 17, 2012 at 7:30 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Christoph, > > It is a good question even though it is obvious :-)  No, for the last few > days, I have not been able to build Clang with make -j2 or -j4 - the build > always fails on a ranlib operation. > > Also, on Windows, GNU Make seems to be somewhat broken with respect to >

Hi, I was trying Ninja to build the LLVM sources. I am using cmake version 2.8.8, latest ninja from git and latest LLVM from git. Here's what I tried: $ cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=... /path/to/src $ ninja $ ninja install The installation aborted with the message below: CMake Error at utils/TableGen/cmake_install.cmake:36 (FILE): file INSTALL cannot

"Sahasrabuddhe, Sameer" <Sameer.Sahasrabuddhe at amd.com> writes: > I was trying Ninja to build the LLVM sources. I am using cmake version > 2.8.8, latest ninja from git and latest LLVM from git. As cmake and ninja development is not coordinated, it is not a good idea to mix versions of them separated by several months. Nor is a good idea to use a development version of

On further thought, I assume this issue actually hits everyone - it's not just Ninja getting in the way, but lit as well. (which also means we'd probably need to fix both Ninja and lit to resolve this issue - but everyone should at least be a little invested in fixing lit). On Sun, Jan 6, 2013 at 12:18 AM, Sean Silva <silvas at purdue.edu> wrote: > Nope. An easy solution (both

IMO, any functional/correctness difference between an incremental and clean build should be considered a build system bug, especially for C++ projects where incremental vs. clean can mean 10 second vs 30 minute build times. -- Sean Silva

On Wed, Feb 6, 2013 at 3:01 PM, Sean Silva <silvas at purdue.edu> wrote: > IMO, any functional/correctness difference between an incremental and > clean build should be considered a build system bug, If your (c)makefile underspecifies dependencies, there's nothing the build system can do. > especially for > C++ projects where incremental vs. clean can mean 10 second vs 30

To whom it may concern: I've been monitoring the lab.llvm.org builders for a bit over a week now and this builder: http://lab.llvm.org:8011/builders/lldb-amd64-ninja-netbsd7 has been down since April. It also has no admin listed. Could it be removedfrom thelist of builders? Sean -------------- next part -------------- An HTML attachment was scrubbed... URL:

So I manage to get clang's colored output through ninja simply by force (CMAKE_CXX_FLAGS=-fcolor-diagnostics), which isn't ideal (if I were to pipe ninja's output to a file it'd still have color escapes, etc) but it works. But I haven't found a similar solution for FileCheck & I'm wondering has anyone already solved this problem for themselves - if so, how? if not,

> It worked and "ninja install" put the stuff in the right target directory but > clang-analyzer is not there. Does anybody know why that happened > with a Cmake build? I've never used the clang-analyzer but I presume you're talking about the stuff in ``tools/scan-view`` and ``tools/scan-build``? There's no CMakeLists.txt files in those directories and I can't

Hello there, on a CentOS 6 box, in the need for `meson`, I've installed rh-python36 using yum, then meson and ninja using `pip3.6 install meson ninja`. Later at run-time, while building atk 2.29.1: $ meson --prefix /opt/atk _build $ ninja-build -C _build FAILED: atk/atkmarshal.c /opt/gimp-2.8/bin/glib-genmarshal --prefix atk_marshal --output atk/atkmarshal.c --body ../atk/atkmarshal.list

I'm in charge of developing a huge music project. Streaming audio content broadcasting multiple channels, live events, dynamically generated playlists, and more will be a feature of the site. I've installed Icecast and spent a lot of time trying to get it functional without much success. I have a massive amount of stuff to coordinate so I'm looking for help to get this thing