similar to: Re: No wine-pthread in 1.1.19 ?

I'm on Opensuse 11.0, just installed Wine 1.1.19 and there's no wine-pthread binary. So i downloaded sources, compiled and again no wine-pthread. What should I do to get this file? Is multithreading dropped in Wine now?

I have done some reading and gather than wine-pthread was dropped somewhere around 1.1.19. Problem I have is that I have an application (newsleecher) which effectively never starts up (gave it 10 minutes at one point, used 100% cpu the whole time) with strait wine command on the older wine version, I think 1.0.something, came with ubuntu 8.04 in one of the unsupported repositories. It starts up

vitamin wrote: > > "wine-pthread" was removed indeed as it's now integrated into loader as the only remaining option. The reason I'm asking is because in some games it is reported that using wine-pthread increases the performance in some games. So how do I enable it, or is it enabled now by default? Or is it integrated in the sense that it has merged together and

Hi All, I am first time trying build CLANG+LLVM using cmake+ninja build system. I updated all my CLANG+LLVM sources to current trunk, and I successfully built it using classic *make* build system. But, trying to build the same with cmake+ninja build system resulting in following build failures for compiler-rt sources. Am I missing something basics here? ==================== cmake command used:

I use latest cmake+ninja which are built from latest sources. ================================= > cmake --version cmake version 2.8.9.20121011-g2876 ================================= -- mahesha On Fri, Oct 12, 2012 at 7:35 PM, Mahesha HS <mahesha.llvm at gmail.com> wrote: > Hi All, > > I am first time trying build CLANG+LLVM using cmake+ninja build > system. I updated all

I'm seeing this too. CC'ing the author ubsan stuff. Richard, I know you were OK with only supporting Clang-bootstraps, but I don't think that's terribly viable here. We should be able to build ubsan's runtime with standards conforming code unless there is some fairly extreme reason not to... On Fri, Oct 12, 2012 at 7:19 AM, Mahesha HS <mahesha.llvm at gmail.com> wrote:

On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com> wrote: > I'm seeing this too. CC'ing the author ubsan stuff. > > Richard, I know you were OK with only supporting Clang-bootstraps, but I > don't think that's terribly viable here. Just out of curiosity - why isn't that viable? I'd sort of hope to treat optional sanitizer runtimes

Hi All, I am trying to build the 'lld' linker on Mac OS 10.9, but during the build, I am getting the errors. Following are the steps that I have followed: 1.     I have downloaded the ‘llvm-stable’ source code from the following location:   https://github.com/llvm-mirror/llvm/tree/stable   2.     Machine details(on which llvm source code isbeing built) are as follows: $ sw_vers

On Sat, Oct 13, 2012 at 1:09 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Fri, Oct 12, 2012 at 6:14 PM, Chandler Carruth <chandlerc at google.com> > wrote: > > I'm seeing this too. CC'ing the author ubsan stuff. > > > > Richard, I know you were OK with only supporting Clang-bootstraps, but I > > don't think that's terribly viable

On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > This file is for configure+make build, not CMake, so I'm not sure why > it's being included into your build (these failures aren't > reproducible for me). > Can you please list the exact steps you're doing to build LLVM with > CMake and make sure you don't have additional CFLAGS (LDFLAGS etc)

Just to prove it, I replied to my own message...AND sent it to myself. What a day... -------- Original Message -------- Subject: Re: [Wine] Errors running BiblePro and BibleStudyPro on today's Git Date: Thu, 11 Feb 2010 20:07:43 -0700 From: James McKenzie <jjmckenzie51 at earthlink.net> To: James Mckenzie <jjmckenzie51 at earthlink.net> References:

On Mon, Nov 11, 2013 at 11:03:47AM -0500, Jack Howarth wrote: > On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > > This file is for configure+make build, not CMake, so I'm not sure why > > it's being included into your build (these failures aren't > > reproducible for me). > > Can you please list the exact steps you're doing to build

+Bob Wilson I don't know if this is a recent Apple regression, or if it's now catching something which had always been invalid. -bw On Mon, Nov 11, 2013 at 8:44 AM, Jack Howarth <howarth at bromo.med.uc.edu>wrote: > On Mon, Nov 11, 2013 at 11:03:47AM -0500, Jack Howarth wrote: > > On Mon, Nov 11, 2013 at 06:46:47PM +0400, Alexander Potapenko wrote: > > > This

Try llvmgcc pthread.c -o pthread.ll -pthread You have to link in the pthreads library, and I believe -pthread is all you need on a redhat 9 box. Kevin > -----Original Message----- > From: llvmdev-admin at cs.uiuc.edu [mailto:llvmdev-admin at cs.uiuc.edu] On > Behalf Of yue > Sent: Tuesday, December 23, 2003 11:43 PM > To: llvmdev at cs.uiuc.edu > Subject: [LLVMdev] pthread?

I try to run lli with "--load=/lib/libpthread.so", but it shows: --------------------------------------------------- [yue at RH9 test]$ ./pthread.ll Error opening '/lib/libpthread.so.0': /lib/libpthread.so.0: symbol _errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference -load request ignored. Creating thread 0 WARNING: Cannot resolve fn

On Wed, 24 Dec 2003, yue wrote: > I try to run lli with "--load=/lib/libpthread.so", but it shows: > --------------------------------------------------- > [yue at RH9 test]$ ./pthread.ll > Error opening '/lib/libpthread.so.0': /lib/libpthread.so.0: symbol > _errno, version GLIBC_2.0 not defined in file libc.so.6 with link time > reference > -load request

hi, I compile a pthread program using llvmgcc, but when i run pthread.ll, it show: ------------------ [yue at RH9 test]$ llvmgcc pthread.c -o pthread.ll [yue at RH9 test]$ ls pthread pthread.c pthread.ll pthread.ll.bc [yue at RH9 test]$ ./pthread.ll Creating thread 0 WARNING: Cannot resolve fn 'pthread_create' using a dummy noop function instead! ERROR; return code from

Hi folks! I'm trying to get rid of any dependency on libgcc*, but without success so far. The following commands were executed on a freshliy installed and updated Ubuntu 16.04 LTS: === snip === sudo apt-get install build-essential libffi-dev cmake # see aptget.txt for packages installed sudo mv /usr/local /usr/local.orig git clone https://github.com/llvm/llvm-project.git cd llvm-project; git

On Thu, Oct 1, 2015 at 10:55 AM, Rui Ueyama via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I honestly think that the ulimit of 1024 max threads is too strict for 48 > core machine. Processes are independent each other, so it is not strange > for them to spawn as many threads as the number of cores. What's the reason > you cannot increase the limit? > Yeah, this is

Marvin_Arnold wrote: > > Charles Davis wrote: > > James McKenzie wrote: > > > > > vitamin wrote: > > > > > > > James McKenzie wrote: > > > > > > > > > > > > > I do think this is doable, but the appropriate variables have to be set before running Wine, just like you do in Linux (or any other UNIX for that